5G NR FR2 beam management enhancements

ABSTRACT

Apparatuses, systems, and methods for a user equipment device (UE) to perform methods for Fifth Generation New Radio (5G NR) frequency range two (FR2) based communications beam management. The UE may configure, via communications with a base station, serving the UE, a group ID for PUCCH resources within a group of PUCCHs, e.g., for FR2 based communications. The UE may receive, from the base station, an update to one or more PUCCH resources within the group of PUCCHs via a medium access control (MAC) control element (CE) that may include one of a resource ID indicating an update to a PUCCH resource or the group ID to update the group of PUCCH resources. The UE may update, based on the MAC-CE, the one or more PUCCH resources within the group of PUCCHs.

PRIORITY DATA

This application is a continuation of U.S. patent application Ser. No.17/021,136, titled “5G NR FR2 Beam Management Enhancements”, filed Sep.15, 2020, now U.S. Pat. No. 11,330,668, which claims benefit of priorityto U.S. Provisional Application Ser. No. 62/939,215, titled “5G NR FR2Beam Management Enhancements”, filed Nov. 22, 2019, which is herebyincorporated by reference in its entirety as though fully and completelyset forth herein.

FIELD

The present application relates to wireless devices, and moreparticularly to apparatuses, systems, and methods for a wireless deviceto perform methods for Fifth Generation New Radio (5G NR) frequencyrange two (FR2) based communications beam management.

DESCRIPTION OF THE RELATED ART

Wireless communication systems are rapidly growing in usage. In recentyears, wireless devices such as smart phones and tablet computers havebecome increasingly sophisticated. In addition to supporting telephonecalls, many mobile devices now provide access to the internet, email,text messaging, and navigation using the global positioning system(GPS), and are capable of operating sophisticated applications thatutilize these functionalities.

Long Term Evolution (LTE) has become the technology of choice for themajority of wireless network operators worldwide, providing mobilebroadband data and high-speed Internet access to their subscriber base.LTE defines a number of downlink (DL) physical channels, categorized astransport or control channels, to carry information blocks received frommedium access control (MAC) and higher layers. LTE also defines a numberof physical layer channels for the uplink (UL).

For example, LTE defines a Physical Downlink Shared Channel (PDSCH) as aDL transport channel. The PDSCH is the main data-bearing channelallocated to users on a dynamic and opportunistic basis. The PDSCHcarries data in Transport Blocks (TB) corresponding to a MAC protocoldata unit (PDU), passed from the MAC layer to the physical (PHY) layeronce per Transmission Time Interval (TTI). The PDSCH is also used totransmit broadcast information such as System Information Blocks (SIB)and paging messages.

As another example, LTE defines a Physical Downlink Control Channel(PDCCH) as a DL control channel that carries the resource assignment forUEs that are contained in a Downlink Control Information (DCI) message.Multiple PDCCHs can be transmitted in the same subframe using ControlChannel Elements (CCE), each of which is a nine set of four resourceelements known as Resource Element Groups (REG). The PDCCH employsquadrature phase-shift keying (QPSK) modulation, with four QPSK symbolsmapped to each REG. Furthermore, 1, 2, 4, or 8 CCEs can be used for aUE, depending on channel conditions, to ensure sufficient robustness.

Additionally, LTE defines a Physical Uplink Shared Channel (PUSCH) as aUL channel shared by all devices (user equipment, UE) in a radio cell totransmit user data to the network. The scheduling for all UEs is undercontrol of the LTE base station (enhanced Node B, or eNB). The eNB usesthe uplink scheduling grant (DCI format 0) to inform the UE aboutresource block (RB) assignment, and the modulation and coding scheme tobe used. PUSCH typically supports QPSK and quadrature amplitudemodulation (QAM). In addition to user data, the PUSCH also carries anycontrol information necessary to decode the information, such astransport format indicators and multiple-in multiple-out (MIMO)parameters. Control data is multiplexed with information data prior todigital Fourier transform (DFT) spreading.

A proposed next telecommunications standard moving beyond the currentInternational Mobile Telecommunications-Advanced (IMT-Advanced)Standards is called 5th generation mobile networks or 5th generationwireless systems, or 5G for short (otherwise known as 5G-NR for 5G NewRadio, also simply referred to as NR). 5G-NR proposes a higher capacityfor a higher density of mobile broadband users, also supportingdevice-to-device, ultra-reliable, and massive machine communications, aswell as lower latency and lower battery consumption, than current LTEstandards. Further, the 5G-NR standard may allow for less restrictive UEscheduling as compared to current LTE standards. Consequently, effortsare being made in ongoing developments of 5G-NR to take advantage ofhigher throughputs possible at higher frequencies.

SUMMARY

Embodiments relate to apparatuses, systems, and methods for a UE toperform Fifth Generation New Radio (5G NR) frequency range two (FR2)based communications beam management.

In some embodiments, a wireless device, e.g., such as a user equipmentdevice (UE), may be configured to configure, via communications with abase station serving the UE, a group identifier (ID) for physical uplinkcontrol channel (PUCCH) resources within a group of PUCCHs, e.g., forFR2 based communications. In some embodiments, configuring the group IDmay include comprises exchanging radio resource control (RRC) messageswith the base station, e.g., during a PUCCH configuration procedure.Additionally, the UE may receive, from the base station, an update toone or more PUCCH resources within the group of PUCCHs via a mediumaccess control (MAC) control element (CE). In some embodiments, the MACCE may include one of a resource ID indicating an update to a PUCCHresource or the group ID to update the group of PUCCH resources. In someembodiments, the UE may update, based on the MAC-CE, the one or morePUCCH resources within the group of PUCCHs.

The techniques described herein may be implemented in and/or used with anumber of different types of devices, including but not limited tocellular phones, tablet computers, wearable computing devices, portablemedia players, and any of various other computing devices.

This Summary is intended to provide a brief overview of some of thesubject matter described in this document. Accordingly, it will beappreciated that the above-described features are merely examples andshould not be construed to narrow the scope or spirit of the subjectmatter described herein in any way. Other features, aspects, andadvantages of the subject matter described herein will become apparentfrom the following Detailed Description, Figures, and Claims.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present subject matter can be obtainedwhen the following detailed description of various embodiments isconsidered in conjunction with the following drawings, in which:

FIG. 1A illustrates an example wireless communication system accordingto some embodiments.

FIG. 1B illustrates an example of a base station (BS) and an accesspoint in communication with a user equipment (UE) device according tosome embodiments.

FIG. 2 illustrates an example simplified block diagram of a WLAN AccessPoint (AP), according to some embodiments.

FIG. 3 illustrates an example block diagram of a UE according to someembodiments.

FIG. 4 illustrates an example block diagram of a BS according to someembodiments.

FIG. 5 illustrates an example block diagram of cellular communicationcircuitry, according to some embodiments.

FIG. 6A illustrates an example of connections between an EPC network, anLTE base station (eNB), and a 5G NR base station (gNB).

FIG. 6B illustrates an example of a protocol stack for an eNB and a gNB.

FIG. 7A illustrates an example of a 5G network architecture thatincorporates both 3GPP (e.g., cellular) and non-3GPP (e.g.,non-cellular) access to the 5G CN, according to some embodiments.

FIG. 7B illustrates an example of a 5G network architecture thatincorporates both dual 3GPP (e.g., LTE and 5G NR) access and non-3GPPaccess to the 5G CN, according to some embodiments.

FIG. 8 illustrates an example of a baseband processor architecture for aUE, according to some embodiments.

FIG. 9 illustrates signaling between a base station and a UE toestablish a beam and associated logical antenna panel ID, according tosome embodiments.

FIG. 10 illustrates a multiple antenna panel UE switching panel states,according to some embodiments.

FIG. 11 illustrates a timeline for pathloss measurement RSreconfiguration, according to some embodiments.

FIGS. 12-18 illustrate block diagrams of examples of methods for FifthGeneration New Radio (5G NR) frequency range two (FR2) basedcommunications beam management, according to some embodiments.

While the features described herein may be susceptible to variousmodifications and alternative forms, specific embodiments thereof areshown by way of example in the drawings and are herein described indetail. It should be understood, however, that the drawings and detaileddescription thereto are not intended to be limiting to the particularform disclosed, but on the contrary, the intention is to cover allmodifications, equivalents and alternatives falling within the spiritand scope of the subject matter as defined by the appended claims.

DETAILED DESCRIPTION Terms

The following is a glossary of terms used in this disclosure:

-   -   Memory Medium—Any of various types of non-transitory memory        devices or storage devices. The term “memory medium” is intended        to include an installation medium, e.g., a CD-ROM, floppy disks,        or tape device; a computer system memory or random-access memory        such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; a        non-volatile memory such as a Flash, magnetic media, e.g., a        hard drive, or optical storage; registers, or other similar        types of memory elements, etc. The memory medium may include        other types of non-transitory memory as well or combinations        thereof. In addition, the memory medium may be located in a        first computer system in which the programs are executed, or may        be located in a second different computer system which connects        to the first computer system over a network, such as the        Internet. In the latter instance, the second computer system may        provide program instructions to the first computer for        execution. The term “memory medium” may include two or more        memory mediums which may reside in different locations, e.g., in        different computer systems that are connected over a network.        The memory medium may store program instructions (e.g., embodied        as computer programs) that may be executed by one or more        processors.    -   Carrier Medium—a memory medium as described above, as well as a        physical transmission medium, such as a bus, network, and/or        other physical transmission medium that conveys signals such as        electrical, electromagnetic, or digital signals.    -   Programmable Hardware Element—includes various hardware devices        comprising multiple programmable function blocks connected via a        programmable interconnect. Examples include FPGAs (Field        Programmable Gate Arrays), PLDs (Programmable Logic Devices),        FPOAs (Field Programmable Object Arrays), and CPLDs (Complex        PLDs). The programmable function blocks may range from fine        grained (combinatorial logic or look up tables) to coarse        grained (arithmetic logic units or processor cores). A        programmable hardware element may also be referred to as        “reconfigurable logic”.    -   Computer System—any of various types of computing or processing        systems, including a personal computer system (PC), mainframe        computer system, workstation, network appliance, Internet        appliance, personal digital assistant (PDA), television system,        grid computing system, or other device or combinations of        devices. In general, the term “computer system” can be broadly        defined to encompass any device (or combination of devices)        having at least one processor that executes instructions from a        memory medium.    -   User Equipment (UE) (or “UE Device”)—any of various types of        computer systems devices which are mobile or portable and which        performs wireless communications. Examples of UE devices include        mobile telephones or smart phones (e.g., iPhone™, Android™-based        phones), portable gaming devices (e.g., Nintendo DS™ PlayStation        Portable™, Gameboy Advance™, iPhone™), laptops, wearable devices        (e.g. smart watch, smart glasses), PDAs, portable Internet        devices, music players, data storage devices, or other handheld        devices, etc. In general, the term “UE” or “UE device” can be        broadly defined to encompass any electronic, computing, and/or        telecommunications device (or combination of devices) which is        easily transported by a user and capable of wireless        communication.    -   Base Station—The term “Base Station” has the full breadth of its        ordinary meaning, and at least includes a wireless communication        station installed at a fixed location and used to communicate as        part of a wireless telephone system or radio system.    -   Processing Element—refers to various elements or combinations of        elements that are capable of performing a function in a device,        such as a user equipment or a cellular network device.        Processing elements may include, for example: processors and        associated memory, portions or circuits of individual processor        cores, entire processor cores, processor arrays, circuits such        as an ASIC (Application Specific Integrated Circuit),        programmable hardware elements such as a field programmable gate        array (FPGA), as well any of various combinations of the above.    -   Channel—a medium used to convey information from a sender        (transmitter) to a receiver. It should be noted that since        characteristics of the term “channel” may differ according to        different wireless protocols, the term “channel” as used herein        may be considered as being used in a manner that is consistent        with the standard of the type of device with reference to which        the term is used. In some standards, channel widths may be        variable (e.g., depending on device capability, band conditions,        etc.). For example, LTE may support scalable channel bandwidths        from 1.4 MHz to 20 MHz. In contrast, WLAN channels may be 22 MHz        wide while Bluetooth channels may be 1 Mhz wide. Other protocols        and standards may include different definitions of channels.        Furthermore, some standards may define and use multiple types of        channels, e.g., different channels for uplink or downlink and/or        different channels for different uses such as data, control        information, etc.    -   Band—The term “band” has the full breadth of its ordinary        meaning, and at least includes a section of spectrum (e.g.,        radio frequency spectrum) in which channels are used or set        aside for the same purpose.    -   Automatically—refers to an action or operation performed by a        computer system (e.g., software executed by the computer system)        or device (e.g., circuitry, programmable hardware elements,        ASICs, etc.), without user input directly specifying or        performing the action or operation. Thus the term        “automatically” is in contrast to an operation being manually        performed or specified by the user, where the user provides        input to directly perform the operation. An automatic procedure        may be initiated by input provided by the user, but the        subsequent actions that are performed “automatically” are not        specified by the user, i.e., are not performed “manually”, where        the user specifies each action to perform. For example, a user        filling out an electronic form by selecting each field and        providing input specifying information (e.g., by typing        information, selecting check boxes, radio selections, etc.) is        filling out the form manually, even though the computer system        must update the form in response to the user actions. The form        may be automatically filled out by the computer system where the        computer system (e.g., software executing on the computer        system) analyzes the fields of the form and fills in the form        without any user input specifying the answers to the fields. As        indicated above, the user may invoke the automatic filling of        the form, but is not involved in the actual filling of the form        (e.g., the user is not manually specifying answers to fields but        rather they are being automatically completed). The present        specification provides various examples of operations being        automatically performed in response to actions the user has        taken.    -   Approximately—refers to a value that is almost correct or exact.        For example, approximately may refer to a value that is within 1        to 10 percent of the exact (or desired) value. It should be        noted, however, that the actual threshold value (or tolerance)        may be application dependent. For example, in some embodiments,        “approximately” may mean within 0.1% of some specified or        desired value, while in various other embodiments, the threshold        may be, for example, 2%, 3%, 5%, and so forth, as desired or as        required by the particular application.    -   Concurrent—refers to parallel execution or performance, where        tasks, processes, or programs are performed in an at least        partially overlapping manner. For example, concurrency may be        implemented using “strong” or strict parallelism, where tasks        are performed (at least partially) in parallel on respective        computational elements, or using “weak parallelism”, where the        tasks are performed in an interleaved manner, e.g., by time        multiplexing of execution threads.

Various components may be described as “configured to” perform a task ortasks. In such contexts, “configured to” is a broad recitation generallymeaning “having structure that” performs the task or tasks duringoperation. As such, the component can be configured to perform the taskeven when the component is not currently performing that task (e.g., aset of electrical conductors may be configured to electrically connect amodule to another module, even when the two modules are not connected).In some contexts, “configured to” may be a broad recitation of structuregenerally meaning “having circuitry that” performs the task or tasksduring operation. As such, the component can be configured to performthe task even when the component is not currently on. In general, thecircuitry that forms the structure corresponding to “configured to” mayinclude hardware circuits.

Various components may be described as performing a task or tasks, forconvenience in the description. Such descriptions should be interpretedas including the phrase “configured to.” Reciting a component that isconfigured to perform one or more tasks is expressly intended not toinvoke 35 U.S.C. § 112(f) interpretation for that component.

FIGS. 1A and 1B—Communication Systems

FIG. 1A illustrates a simplified example wireless communication system,according to some embodiments. It is noted that the system of FIG. 1 ismerely one example of a possible system, and that features of thisdisclosure may be implemented in any of various systems, as desired.

As shown, the example wireless communication system includes a basestation 102A which communicates over a transmission medium with one ormore user devices 106A, 106B, etc., through 106N. Each of the userdevices may be referred to herein as a “user equipment” (UE). Thus, theuser devices 106 are referred to as UEs or UE devices.

The base station (BS) 102A may be a base transceiver station (BTS) orcell site (a “cellular base station”) and may include hardware thatenables wireless communication with the UEs 106A through 106N.

The communication area (or coverage area) of the base station may bereferred to as a “cell.” The base station 102A and the UEs 106 may beconfigured to communicate over the transmission medium using any ofvarious radio access technologies (RATs), also referred to as wirelesscommunication technologies, or telecommunication standards, such as GSM,UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces),LTE, LTE-Advanced (LTE-A), 5G new radio (5G NR), HSPA, 3GPP2 CDMA2000(e.g., 1×RTT, 1×EV-DO, HRPD, eHRPD), etc. Note that if the base station102A is implemented in the context of LTE, it may alternately bereferred to as an ‘eNodeB’ or ‘eNB’. Note that if the base station 102Ais implemented in the context of 5G NR, it may alternately be referredto as ‘gNodeB’ or ‘gNB’.

As shown, the base station 102A may also be equipped to communicate witha network 100 (e.g., a core network of a cellular service provider, atelecommunication network such as a public switched telephone network(PSTN), and/or the Internet, among various possibilities). Thus, thebase station 102A may facilitate communication between the user devicesand/or between the user devices and the network 100. In particular, thecellular base station 102A may provide UEs 106 with varioustelecommunication capabilities, such as voice, SMS and/or data services.

Base station 102A and other similar base stations (such as base stations102B . . . 102N) operating according to the same or a different cellularcommunication standard may thus be provided as a network of cells, whichmay provide continuous or nearly continuous overlapping service to UEs106A-N and similar devices over a geographic area via one or morecellular communication standards.

Thus, while base station 102A may act as a “serving cell” for UEs 106A-Nas illustrated in FIG. 1 , each UE 106 may also be capable of receivingsignals from (and possibly within communication range of) one or moreother cells (which might be provided by base stations 102B-N and/or anyother base stations), which may be referred to as “neighboring cells”.Such cells may also be capable of facilitating communication betweenuser devices and/or between user devices and the network 100. Such cellsmay include “macro” cells, “micro” cells, “pico” cells, and/or cellswhich provide any of various other granularities of service area size.For example, base stations 102A-B illustrated in FIG. 1 might be macrocells, while base station 102N might be a micro cell. Otherconfigurations are also possible.

In some embodiments, base station 102A may be a next generation basestation, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In someembodiments, a gNB may be connected to a legacy evolved packet core(EPC) network and/or to a NR core (NRC) network. In addition, a gNB cellmay include one or more transition and reception points (TRPs). Inaddition, a UE capable of operating according to 5G NR may be connectedto one or more TRPs within one or more gNBs.

Note that a UE 106 may be capable of communicating using multiplewireless communication standards. For example, the UE 106 may beconfigured to communicate using a wireless networking (e.g., Wi-Fi)and/or peer-to-peer wireless communication protocol (e.g., Bluetooth,Wi-Fi peer-to-peer, etc.) in addition to at least one cellularcommunication protocol (e.g., GSM, UMTS (associated with, for example,WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2CDMA2000 (e.g., 1×RTT, 1×EV-DO, HRPD, eHRPD), etc.). The UE 106 may alsoor alternatively be configured to communicate using one or more globalnavigational satellite systems (GNSS, e.g., GPS or GLONASS), one or moremobile television broadcasting standards (e.g., ATSC-M/H or DVB-H),and/or any other wireless communication protocol, if desired. Othercombinations of wireless communication standards (including more thantwo wireless communication standards) are also possible.

FIG. 1B illustrates user equipment 106 (e.g., one of the devices 106Athrough 106N) in communication with a base station 102 and an accesspoint 112, according to some embodiments. The UE 106 may be a devicewith both cellular communication capability and non-cellularcommunication capability (e.g., Bluetooth, Wi-Fi, and so forth) such asa mobile phone, a hand-held device, a computer or a tablet, or virtuallyany type of wireless device.

The UE 106 may include a processor that is configured to execute programinstructions stored in memory. The UE 106 may perform any of the methodembodiments described herein by executing such stored instructions.Alternatively, or in addition, the UE 106 may include a programmablehardware element such as an FPGA (field-programmable gate array) that isconfigured to perform any of the method embodiments described herein, orany portion of any of the method embodiments described herein.

The UE 106 may include one or more antennas for communicating using oneor more wireless communication protocols or technologies. In someembodiments, the UE 106 may be configured to communicate using, forexample, CDMA2000 (1×RTT/1×EV-DO/HRPD/eHRPD), LTE/LTE-Advanced, or 5G NRusing a single shared radio and/or GSM, LTE, LTE-Advanced, or 5G NRusing the single shared radio. The shared radio may couple to a singleantenna, or may couple to multiple antennas (e.g., for MIMO) forperforming wireless communications. In general, a radio may include anycombination of a baseband processor, analog RF signal processingcircuitry (e.g., including filters, mixers, oscillators, amplifiers,etc.), or digital processing circuitry (e.g., for digital modulation aswell as other digital processing). Similarly, the radio may implementone or more receive and transmit chains using the aforementionedhardware. For example, the UE 106 may share one or more parts of areceive and/or transmit chain between multiple wireless communicationtechnologies, such as those discussed above.

In some embodiments, the UE 106 may include separate transmit and/orreceive chains (e.g., including separate antennas and other radiocomponents) for each wireless communication protocol with which it isconfigured to communicate. As a further possibility, the UE 106 mayinclude one or more radios which are shared between multiple wirelesscommunication protocols, and one or more radios which are usedexclusively by a single wireless communication protocol. For example,the UE 106 might include a shared radio for communicating using eitherof LTE or 5G NR (or LTE or 1×RTT or LTE or GSM), and separate radios forcommunicating using each of Wi-Fi and Bluetooth. Other configurationsare also possible.

FIG. 2 —Access Point Block Diagram

FIG. 2 illustrates an exemplary block diagram of an access point (AP)112. It is noted that the block diagram of the AP of FIG. 2 is only oneexample of a possible system. As shown, the AP 112 may includeprocessor(s) 204 which may execute program instructions for the AP 112.The processor(s) 204 may also be coupled (directly or indirectly) tomemory management unit (MMU) 240, which may be configured to receiveaddresses from the processor(s) 204 and to translate those addresses tolocations in memory (e.g., memory 260 and read only memory (ROM) 250) orto other circuits or devices.

The AP 112 may include at least one network port 270. The network port270 may be configured to couple to a wired network and provide aplurality of devices, such as UEs 106, access to the Internet. Forexample, the network port 270 (or an additional network port) may beconfigured to couple to a local network, such as a home network or anenterprise network. For example, port 270 may be an Ethernet port. Thelocal network may provide connectivity to additional networks, such asthe Internet.

The AP 112 may include at least one antenna 234, which may be configuredto operate as a wireless transceiver and may be further configured tocommunicate with UE 106 via wireless communication circuitry 230. Theantenna 234 communicates with the wireless communication circuitry 230via communication chain 232. Communication chain 232 may include one ormore receive chains, one or more transmit chains or both. The wirelesscommunication circuitry 230 may be configured to communicate via Wi-Fior WLAN, e.g., 802.11. The wireless communication circuitry 230 mayalso, or alternatively, be configured to communicate via various otherwireless communication technologies, including, but not limited to, 5GNR, Long-Term Evolution (LTE), LTE Advanced (LTE-A), Global System forMobile (GSM), Wideband Code Division Multiple Access (WCDMA), CDMA2000,etc., for example when the AP is co-located with a base station in caseof a small cell, or in other instances when it may be desirable for theAP 112 to communicate via various different wireless communicationtechnologies.

In some embodiments, as further described below, an AP 112 may beconfigured to perform methods for 5G NR FR2 based communications beammanagement as further described herein.

FIG. 3 —Block Diagram of a UE

FIG. 3 illustrates an example simplified block diagram of acommunication device 106, according to some embodiments. It is notedthat the block diagram of the communication device of FIG. 3 is only oneexample of a possible communication device. According to embodiments,communication device 106 may be a user equipment (UE) device, a mobiledevice or mobile station, a wireless device or wireless station, adesktop computer or computing device, a mobile computing device (e.g., alaptop, notebook, or portable computing device), a tablet and/or acombination of devices, among other devices. As shown, the communicationdevice 106 may include a set of components 300 configured to performcore functions. For example, this set of components may be implementedas a system on chip (SOC), which may include portions for variouspurposes. Alternatively, this set of components 300 may be implementedas separate components or groups of components for the various purposes.The set of components 300 may be coupled (e.g., communicatively;directly or indirectly) to various other circuits of the communicationdevice 106.

For example, the communication device 106 may include various types ofmemory (e.g., including NAND flash 310), an input/output interface suchas connector I/F 320 (e.g., for connecting to a computer system; dock;charging station; input devices, such as a microphone, camera, keyboard;output devices, such as speakers; etc.), the display 360, which may beintegrated with or external to the communication device 106, andcellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc.,and short to medium range wireless communication circuitry 329 (e.g.,Bluetooth™ and WLAN circuitry). In some embodiments, communicationdevice 106 may include wired communication circuitry (not shown), suchas a network interface card, e.g., for Ethernet.

The cellular communication circuitry 330 may couple (e.g.,communicatively; directly or indirectly) to one or more antennas, suchas antennas 335 and 336 as shown. The short to medium range wirelesscommunication circuitry 329 may also couple (e.g., communicatively;directly or indirectly) to one or more antennas, such as antennas 337and 338 as shown. Alternatively, the short to medium range wirelesscommunication circuitry 329 may couple (e.g., communicatively; directlyor indirectly) to the antennas 335 and 336 in addition to, or insteadof, coupling (e.g., communicatively; directly or indirectly) to theantennas 337 and 338. The short to medium range wireless communicationcircuitry 329 and/or cellular communication circuitry 330 may includemultiple receive chains and/or multiple transmit chains for receivingand/or transmitting multiple spatial streams, such as in amultiple-input multiple output (MIMO) configuration.

In some embodiments, as further described below, cellular communicationcircuitry 330 may include dedicated receive chains (including and/orcoupled to, e.g., communicatively; directly or indirectly, dedicatedprocessors and/or radios) for multiple RATs (e.g., a first receive chainfor LTE and a second receive chain for 5G NR). In addition, in someembodiments, cellular communication circuitry 330 may include a singletransmit chain that may be switched between radios dedicated to specificRATs. For example, a first radio may be dedicated to a first RAT, e.g.,LTE, and may be in communication with a dedicated receive chain and atransmit chain shared with an additional radio, e.g., a second radiothat may be dedicated to a second RAT, e.g., 5G NR, and may be incommunication with a dedicated receive chain and the shared transmitchain.

The communication device 106 may also include and/or be configured foruse with one or more user interface elements. The user interfaceelements may include any of various elements, such as display 360 (whichmay be a touchscreen display), a keyboard (which may be a discretekeyboard or may be implemented as part of a touchscreen display), amouse, a microphone and/or speakers, one or more cameras, one or morebuttons, and/or any of various other elements capable of providinginformation to a user and/or receiving or interpreting user input.

The communication device 106 may further include one or more smart cards345 that include SIM (Subscriber Identity Module) functionality, such asone or more UICC(s) (Universal Integrated Circuit Card(s)) cards 345.

As shown, the SOC 300 may include processor(s) 302, which may executeprogram instructions for the communication device 106 and displaycircuitry 304, which may perform graphics processing and provide displaysignals to the display 360. The processor(s) 302 may also be coupled tomemory management unit (MMU) 340, which may be configured to receiveaddresses from the processor(s) 302 and translate those addresses tolocations in memory (e.g., memory 306, read only memory (ROM) 350, NANDflash memory 310) and/or to other circuits or devices, such as thedisplay circuitry 304, short to medium range wireless communicationcircuitry 329, cellular communication circuitry 330, connector I/F 320,and/or display 360. The MMU 340 may be configured to perform memoryprotection and page table translation or set up. In some embodiments,the MMU 340 may be included as a portion of the processor(s) 302.

As noted above, the communication device 106 may be configured tocommunicate using wireless and/or wired communication circuitry. Thecommunication device 106 may be configured to perform methods for 5G NRFR2 based communications beam management as further described herein.

As described herein, the communication device 106 may include hardwareand software components for implementing the above features for acommunication device 106 to communicate a scheduling profile for powersavings to a network. The processor 302 of the communication device 106may be configured to implement part or all of the features describedherein, e.g., by executing program instructions stored on a memorymedium (e.g., a non-transitory computer-readable memory medium).Alternatively (or in addition), processor 302 may be configured as aprogrammable hardware element, such as an FPGA (Field Programmable GateArray), or as an ASIC (Application Specific Integrated Circuit).Alternatively (or in addition) the processor 302 of the communicationdevice 106, in conjunction with one or more of the other components 300,304, 306, 310, 320, 329, 330, 340, 345, 350, 360 may be configured toimplement part or all of the features described herein.

In addition, as described herein, processor 302 may include one or moreprocessing elements. Thus, processor 302 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processor 302. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processor(s) 302.

Further, as described herein, cellular communication circuitry 330 andshort to medium range wireless communication circuitry 329 may eachinclude one or more processing elements. In other words, one or moreprocessing elements may be included in cellular communication circuitry330 and, similarly, one or more processing elements may be included inshort to medium range wireless communication circuitry 329. Thus,cellular communication circuitry 330 may include one or more integratedcircuits (ICs) that are configured to perform the functions of cellularcommunication circuitry 330. In addition, each integrated circuit mayinclude circuitry (e.g., first circuitry, second circuitry, etc.)configured to perform the functions of cellular communication circuitry330. Similarly, the short to medium range wireless communicationcircuitry 329 may include one or more ICs that are configured to performthe functions of short to medium range wireless communication circuitry329. In addition, each integrated circuit may include circuitry (e.g.,first circuitry, second circuitry, etc.) configured to perform thefunctions of short to medium range wireless communication circuitry 329.

FIG. 4 —Block Diagram of a Base Station

FIG. 4 illustrates an example block diagram of a base station 102,according to some embodiments. It is noted that the base station of FIG.4 is merely one example of a possible base station. As shown, the basestation 102 may include processor(s) 404 which may execute programinstructions for the base station 102. The processor(s) 404 may also becoupled to memory management unit (MMU) 440, which may be configured toreceive addresses from the processor(s) 404 and translate thoseaddresses to locations in memory (e.g., memory 460 and read only memory(ROM) 450) or to other circuits or devices.

The base station 102 may include at least one network port 470. Thenetwork port 470 may be configured to couple to a telephone network andprovide a plurality of devices, such as UE devices 106, access to thetelephone network as described above in FIGS. 1 and 2 .

The network port 470 (or an additional network port) may also oralternatively be configured to couple to a cellular network, e.g., acore network of a cellular service provider. The core network mayprovide mobility related services and/or other services to a pluralityof devices, such as UE devices 106. In some cases, the network port 470may couple to a telephone network via the core network, and/or the corenetwork may provide a telephone network (e.g., among other UE devicesserviced by the cellular service provider).

In some embodiments, base station 102 may be a next generation basestation, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In suchembodiments, base station 102 may be connected to a legacy evolvedpacket core (EPC) network and/or to a NR core (NRC) network. Inaddition, base station 102 may be considered a 5G NR cell and mayinclude one or more transition and reception points (TRPs). In addition,a UE capable of operating according to 5G NR may be connected to one ormore TRPs within one or more gNB s.

The base station 102 may include at least one antenna 434, and possiblymultiple antennas. The at least one antenna 434 may be configured tooperate as a wireless transceiver and may be further configured tocommunicate with UE devices 106 via radio 430. The antenna 434communicates with the radio 430 via communication chain 432.Communication chain 432 may be a receive chain, a transmit chain orboth. The radio 430 may be configured to communicate via variouswireless communication standards, including, but not limited to, 5G NR,LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

The base station 102 may be configured to communicate wirelessly usingmultiple wireless communication standards. In some instances, the basestation 102 may include multiple radios, which may enable the basestation 102 to communicate according to multiple wireless communicationtechnologies. For example, as one possibility, the base station 102 mayinclude an LTE radio for performing communication according to LTE aswell as a 5G NR radio for performing communication according to 5G NR.In such a case, the base station 102 may be capable of operating as bothan LTE base station and a 5G NR base station. As another possibility,the base station 102 may include a multi-mode radio which is capable ofperforming communications according to any of multiple wirelesscommunication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTEand UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

As described further subsequently herein, the BS 102 may includehardware and software components for implementing or supportingimplementation of features described herein. The processor 404 of thebase station 102 may be configured to implement or supportimplementation of part or all of the methods described herein, e.g., byexecuting program instructions stored on a memory medium (e.g., anon-transitory computer-readable memory medium). Alternatively, theprocessor 404 may be configured as a programmable hardware element, suchas an FPGA (Field Programmable Gate Array), or as an ASIC (ApplicationSpecific Integrated Circuit), or a combination thereof. Alternatively(or in addition) the processor 404 of the BS 102, in conjunction withone or more of the other components 430, 432, 434, 440, 450, 460, 470may be configured to implement or support implementation of part or allof the features described herein.

In addition, as described herein, processor(s) 404 may be comprised ofone or more processing elements. In other words, one or more processingelements may be included in processor(s) 404. Thus, processor(s) 404 mayinclude one or more integrated circuits (ICs) that are configured toperform the functions of processor(s) 404. In addition, each integratedcircuit may include circuitry (e.g., first circuitry, second circuitry,etc.) configured to perform the functions of processor(s) 404.

Further, as described herein, radio 430 may be comprised of one or moreprocessing elements. In other words, one or more processing elements maybe included in radio 430. Thus, radio 430 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof radio 430. In addition, each integrated circuit may include circuitry(e.g., first circuitry, second circuitry, etc.) configured to performthe functions of radio 430.

FIG. 5 : Block Diagram of Cellular Communication Circuitry

FIG. 5 illustrates an example simplified block diagram of cellularcommunication circuitry, according to some embodiments. It is noted thatthe block diagram of the cellular communication circuitry of FIG. 5 isonly one example of a possible cellular communication circuit. Accordingto embodiments, cellular communication circuitry 330 may be included ina communication device, such as communication device 106 describedabove. As noted above, communication device 106 may be a user equipment(UE) device, a mobile device or mobile station, a wireless device orwireless station, a desktop computer or computing device, a mobilecomputing device (e.g., a laptop, notebook, or portable computingdevice), a tablet and/or a combination of devices, among other devices.

The cellular communication circuitry 330 may couple (e.g.,communicatively; directly or indirectly) to one or more antennas, suchas antennas 335 a-b and 336 as shown (in FIG. 3 ). In some embodiments,cellular communication circuitry 330 may include dedicated receivechains (including and/or coupled to, e.g., communicatively; directly orindirectly, dedicated processors and/or radios) for multiple RATs (e.g.,a first receive chain for LTE and a second receive chain for 5G NR). Forexample, as shown in FIG. 5 , cellular communication circuitry 330 mayinclude a modem 510 and a modem 520. Modem 510 may be configured forcommunications according to a first RAT, e.g., such as LTE or LTE-A, andmodem 520 may be configured for communications according to a secondRAT, e.g., such as 5G NR.

As shown, modem 510 may include one or more processors 512 and a memory516 in communication with processors 512. Modem 510 may be incommunication with a radio frequency (RF) front end 530. RF front end530 may include circuitry for transmitting and receiving radio signals.For example, RF front end 530 may include receive circuitry (RX) 532 andtransmit circuitry (TX) 534. In some embodiments, receive circuitry 532may be in communication with downlink (DL) front end 550, which mayinclude circuitry for receiving radio signals via antenna 335 a.

Similarly, modem 520 may include one or more processors 522 and a memory526 in communication with processors 522. Modem 520 may be incommunication with an RF front end 540. RF front end 540 may includecircuitry for transmitting and receiving radio signals. For example, RFfront end 540 may include receive circuitry 542 and transmit circuitry544. In some embodiments, receive circuitry 542 may be in communicationwith DL front end 560, which may include circuitry for receiving radiosignals via antenna 335 b.

In some embodiments, a switch 570 may couple transmit circuitry 534 touplink (UL) front end 572. In addition, switch 570 may couple transmitcircuitry 544 to UL front end 572. UL front end 572 may includecircuitry for transmitting radio signals via antenna 336. Thus, whencellular communication circuitry 330 receives instructions to transmitaccording to the first RAT (e.g., as supported via modem 510), switch570 may be switched to a first state that allows modem 510 to transmitsignals according to the first RAT (e.g., via a transmit chain thatincludes transmit circuitry 534 and UL front end 572). Similarly, whencellular communication circuitry 330 receives instructions to transmitaccording to the second RAT (e.g., as supported via modem 520), switch570 may be switched to a second state that allows modem 520 to transmitsignals according to the second RAT (e.g., via a transmit chain thatincludes transmit circuitry 544 and UL front end 572).

In some embodiments, the cellular communication circuitry 330 may beconfigured to perform methods for 5G NR FR2 based communications beammanagement as further described herein.

As described herein, the modem 510 may include hardware and softwarecomponents for implementing the above features or for time divisionmultiplexing UL data for NSA NR operations, as well as the various othertechniques described herein. The processors 512 may be configured toimplement part or all of the features described herein, e.g., byexecuting program instructions stored on a memory medium (e.g., anon-transitory computer-readable memory medium). Alternatively (or inaddition), processor 512 may be configured as a programmable hardwareelement, such as an FPGA (Field Programmable Gate Array), or as an ASIC(Application Specific Integrated Circuit). Alternatively (or inaddition) the processor 512, in conjunction with one or more of theother components 530, 532, 534, 550, 570, 572, 335 and 336 may beconfigured to implement part or all of the features described herein.

In addition, as described herein, processors 512 may include one or moreprocessing elements. Thus, processors 512 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processors 512. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processors 512.

As described herein, the modem 520 may include hardware and softwarecomponents for implementing the above features for communicating ascheduling profile for power savings to a network, as well as thevarious other techniques described herein. The processors 522 may beconfigured to implement part or all of the features described herein,e.g., by executing program instructions stored on a memory medium (e.g.,a non-transitory computer-readable memory medium). Alternatively (or inaddition), processor 522 may be configured as a programmable hardwareelement, such as an FPGA (Field Programmable Gate Array), or as an ASIC(Application Specific Integrated Circuit). Alternatively (or inaddition) the processor 522, in conjunction with one or more of theother components 540, 542, 544, 550, 570, 572, 335 and 336 may beconfigured to implement part or all of the features described herein.

In addition, as described herein, processors 522 may include one or moreprocessing elements. Thus, processors 522 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processors 522. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processors 522.

5G NR Architecture with LTE

In some implementations, fifth generation (5G) wireless communicationwill initially be deployed concurrently with current wirelesscommunication standards (e.g., LTE). For example, dual connectivitybetween LTE and 5G new radio (5G NR or NR) has been specified as part ofthe initial deployment of NR. Thus, as illustrated in FIGS. 6A-B,evolved packet core (EPC) network 600 may continue to communicate withcurrent LTE base stations (e.g., eNB 602). In addition, eNB 602 may bein communication with a 5G NR base station (e.g., gNB 604) and may passdata between the EPC network 600 and gNB 604. Thus, EPC network 600 maybe used (or reused) and gNB 604 may serve as extra capacity for UEs,e.g., for providing increased downlink throughput to UEs. In otherwords, LTE may be used for control plane signaling and NR may be usedfor user plane signaling. Thus, LTE may be used to establish connectionsto the network and NR may be used for data services.

FIG. 6B illustrates a proposed protocol stack for eNB 602 and gNB 604.As shown, eNB 602 may include a medium access control (MAC) layer 632that interfaces with radio link control (RLC) layers 622 a-b. RLC layer622 a may also interface with packet data convergence protocol (PDCP)layer 612 a and RLC layer 622 b may interface with PDCP layer 612 b.Similar to dual connectivity as specified in LTE-Advanced Release 12,PDCP layer 612 a may interface via a master cell group (MCG) bearer withEPC network 600 whereas PDCP layer 612 b may interface via a splitbearer with EPC network 600.

Additionally, as shown, gNB 604 may include a MAC layer 634 thatinterfaces with RLC layers 624 a-b. RLC layer 624 a may interface withPDCP layer 612 b of eNB 602 via an X2 interface for information exchangeand/or coordination (e.g., scheduling of a UE) between eNB 602 and gNB604. In addition, RLC layer 624 b may interface with PDCP layer 614.Similar to dual connectivity as specified in LTE-Advanced Release 12,PDCP layer 614 may interface with EPC network 600 via a secondary cellgroup (SCG) bearer. Thus, eNB 602 may be considered a master node (MeNB)while gNB 604 may be considered a secondary node (SgNB). In somescenarios, a UE may be required to maintain a connection to both an MeNBand a SgNB. In such scenarios, the MeNB may be used to maintain a radioresource control (RRC) connection to an EPC while the SgNB may be usedfor capacity (e.g., additional downlink and/or uplink throughput).

5G Core Network Architecture—Interworking with Wi-Fi

In some embodiments, the 5G core network (CN) may be accessed via (orthrough) a cellular connection/interface (e.g., via a 3GPP communicationarchitecture/protocol) and a non-cellular connection/interface (e.g., anon-3GPP access architecture/protocol such as Wi-Fi connection). FIG. 7Aillustrates an example of a 5G network architecture that incorporatesboth 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access tothe 5G CN, according to some embodiments. As shown, a user equipmentdevice (e.g., such as UE 106) may access the 5G CN through both a radioaccess network (RAN, e.g., such as gNB or base station 604) and anaccess point, such as AP 112. The AP 112 may include a connection to theInternet 700 as well as a connection to a non-3GPP inter-workingfunction (N3IWF) 702 network entity. The N3IWF may include a connectionto a core access and mobility management function (AMF) 704 of the 5GCN. The AMF 704 may include an instance of a 5G mobility management (5GMM) function associated with the UE 106. In addition, the RAN (e.g., gNB604) may also have a connection to the AMF 704. Thus, the 5G CN maysupport unified authentication over both connections as well as allowsimultaneous registration for UE 106 access via both gNB 604 and AP 112.As shown, the AMF 704 may include one or more functional entitiesassociated with the 5G CN (e.g., network slice selection function (NSSF)720, short message service function (SMSF) 722, application function(AF) 724, unified data management (UDM) 726, policy control function(PCF) 728, and/or authentication server function (AUSF) 730). Note thatthese functional entities may also be supported by a session managementfunction (SMF) 706 a and an SMF 706 b of the 5G CN. The AMF 706 may beconnected to (or in communication with) the SMF 706 a. Further, the gNB604 may in communication with (or connected to) a user plane function(UPF) 708 a that may also be communication with the SMF 706 a.Similarly, the N3IWF 702 may be communicating with a UPF 708 b that mayalso be communicating with the SMF 706 b. Both UPFs may be communicatingwith the data network (e.g., DN 710 a and 710 b) and/or the Internet 700and IMS core network 710.

FIG. 7B illustrates an example of a 5G network architecture thatincorporates both dual 3GPP (e.g., LTE and 5G NR) access and non-3GPPaccess to the 5G CN, according to some embodiments. As shown, a userequipment device (e.g., such as UE 106) may access the 5G CN throughboth a radio access network (RAN, e.g., such as gNB or base station 604or eNB or base station 602) and an access point, such as AP 112. The AP112 may include a connection to the Internet 700 as well as a connectionto the N3IWF 702 network entity. The N3IWF may include a connection tothe AMF 704 of the 5G CN. The AMF 704 may include an instance of the 5GMM function associated with the UE 106. In addition, the RAN (e.g., gNB604) may also have a connection to the AMF 704. Thus, the 5G CN maysupport unified authentication over both connections as well as allowsimultaneous registration for UE 106 access via both gNB 604 and AP 112.In addition, the 5G CN may support dual-registration of the UE on both alegacy network (e.g., LTE via base station 602) and a 5G network (e.g.,via base station 604). As shown, the base station 602 may haveconnections to a mobility management entity (MME) 742 and a servinggateway (SGW) 744. The MME 742 may have connections to both the SGW 744and the AMF 704. In addition, the SGW 744 may have connections to boththe SMF 706 a and the UPF 708 a. As shown, the AMF 704 may include oneor more functional entities associated with the 5G CN (e.g., NSSF 720,SMSF 722, AF 724, UDM 726, PCF 728, and/or AUSF 730). Note that UDM 726may also include a home subscriber server (HSS) function and the PCF mayalso include a policy and charging rules function (PCRF). Note furtherthat these functional entities may also be supported by the SMF 706 aand the SMF 706 b of the 5G CN. The AMF 706 may be connected to (or incommunication with) the SMF 706 a. Further, the gNB 604 may incommunication with (or connected to) the UPF 708 a that may also becommunication with the SMF 706 a. Similarly, the N3IWF 702 may becommunicating with a UPF 708 b that may also be communicating with theSMF 706 b. Both UPFs may be communicating with the data network (e.g.,DN 710 a and 710 b) and/or the Internet 700 and IMS core network 710.

Note that in various embodiments, one or more of the above describednetwork entities may be configured to perform methods for 5G NR FR2based communications beam management, e.g., as further described herein.

FIG. 8 illustrates an example of a baseband processor architecture for aUE (e.g., such as UE 106), according to some embodiments. The basebandprocessor architecture 800 described in FIG. 8 may be implemented on oneor more radios (e.g., radios 329 and/or 330 described above) or modems(e.g., modems 510 and/or 520) as described above. As shown, thenon-access stratum (NAS) 810 may include a 5G NAS 820 and a legacy NAS850. The legacy NAS 850 may include a communication connection with alegacy access stratum (AS) 870. The 5G NAS 820 may include communicationconnections with both a 5G AS 840 and a non-3GPP AS 830 and Wi-Fi AS832. The 5G NAS 820 may include functional entities associated with bothaccess stratums. Thus, the 5G NAS 820 may include multiple 5G MMentities 826 and 828 and 5G session management (SM) entities 822 and824. The legacy NAS 850 may include functional entities such as shortmessage service (SMS) entity 852, evolved packet system (EPS) sessionmanagement (ESM) entity 854, session management (SM) entity 856, EPSmobility management (EMM) entity 858, and mobility management (MM)/GPRSmobility management (GMM) entity 860. In addition, the legacy AS 870 mayinclude functional entities such as LTE AS 872, UMTS AS 874, and/orGSM/GPRS AS 876.

Thus, the baseband processor architecture 800 allows for a common 5G-NASfor both 5G cellular and non-cellular (e.g., non-3GPP access). Note thatas shown, the 5G MM may maintain individual connection management andregistration management state machines for each connection.Additionally, a device (e.g., UE 106) may register to a single PLMN(e.g., 5G CN) using 5G cellular access as well as non-cellular access.Further, it may be possible for the device to be in a connected state inone access and an idle state in another access and vice versa. Finally,there may be common 5G-MM procedures (e.g., registration,de-registration, identification, authentication, as so forth) for bothaccesses.

Note that in various embodiments, one or more of the above describedfunctional entities of the 5G NAS and/or 5G AS may be configured toperform methods for 5G NR FR2 based communications beam management,e.g., as further described herein.

5G NR FR2 Beam Management

In current implementations, the air interface defined by 3GPP for 5G NRis subdivided into two frequency ranges. Frequency range 1 (FR1)includes frequencies below 6 GHz and frequency range 2 (FR2) includesfrequencies above 24 GHz (e.g., millimeter wave (mmW) spectrum). In 3GPPRelease 15, the minimum channel bandwidth defined for FR2 is 50 MHz andthe maximum channel bandwidth defined for FR2 is 400 MHz. Due to theanalog beam forming associated with FR2 communications, beam managementdiffers as compared to FR1 communications. In current implementations of3GPP Release 15 only basic beam management solutions are defined. Forexample, 3GPP Release 15 only supports a medium access control (MAC)control element (CE) for update of quasi co-location (QCL) (beam)information for one physical uplink control channel (PUCCH) per MAC-CE.Further, multi-panel support, which may be more important for FR2communications as compared to FR1 communications (e.g., to ensure mmWcoverage due to different device holding positions and/or nearbyblocking objects), has not been optimized for efficient panelmanagement. As yet another example, in current implementations, powercontrol is linked to SRI (sounding reference signal (SRS) resourceindicator) or other reference signals and configured via radio resourcecontrol (RRC) signaling, which may not be optimal for changingconditions that may impact FR2 communications more so than FR1communications.

Embodiments described herein provide systems, methods, and mechanismsfor a user equipment device (UE), such as UE 106, to perform beammanagement for FR2 based communications. In some embodiments, one MAC CEmay update a group of PUCCHs to reduce latency and/or signalingoverhead. In some embodiments, the UE may use a MAC CE to update uplink(UL) power control parameters. In some embodiments, the UE may report alogical antenna panel identifier to a network.

In some embodiments, a PUCCH group identifier (group ID) may be assignedto each PUCCH resource, e.g., to allow a MAC CE to update QCL for agroup of PUCCHs. In some embodiments, a MAC CE may use either a resourceID (e.g., to update a specific PUCCH) or a group ID (e.g., to update agroup of PUCCHs). In some embodiments, a group ID for PUCCH resourcesmay be configured via an RRC message(s), e.g., during PUCCHconfiguration. In some embodiments, the UE may signal a PUCCH resourceID with a PUCCH group ID. In some embodiments, a PUCCH group ID mayreplace a PUCCH resource ID within a MAC CE.

In some embodiments, in cases in which a PUCCH resource ID is not valid(e.g., invalid) and/or is a reserved value, a MAC CE may be interpretedas an update to PUCCH resources configured in a bandwidth part (BWP),e.g., as indicated by a BWP identifier (ID). In some embodiments, thereserved value may be useable to indicate all serving cells instead of(and/or in addition to) the BWP. Thus, such a configuration may allowfor a multiple cell update with a single MAC CE. In some embodiments, incases in which a PUCCH resource ID is not valid (e.g., invalid) and/oris a reserved value, a MAC CE may be interpreted as an update to PUCCHresources configured in a cell indicated by a service cell identifier(ID), e.g., included in the MAC CE.

In some embodiments, after a beam failure condition (BFR), a UE may usea beam identified during a candidate beam search period, e.g., prior toexplicit reconfiguration (by a base station, such as gNB 604) of a PUCCHQCL via RRC signal or a MAC CE. In some embodiments, a default PUCCHgroup ID may be defined and/or specified. In some embodiments, a PUCCHgroup with a smallest PUCCH group ID in a current BWP may be the defaultPUCCH group. In some embodiments, the default PUCCH group may includeservices that are the least delay tolerant, e.g., to minimize datainterruptions due to beam failure. In some embodiments, upon detectionof a beam failure recovery procedure, a PUCCH resource in the defaultPUCCH group may have their QCL (beam) configuration updated with a newlydiscovered beam.

In some embodiments, a UE, such as UE 106, may activate and/ordeactivate antenna panels for transmission, e.g., without input from anetwork. In some embodiments, a UE may report capabilities associatedwith a QCL update. For example, in some embodiments, the UE may report anumber (e.g., a maximum number, in some embodiments) of supportedtransmission configuration indicator (TCI) states across componentcarriers (CCs) within a band. In some embodiments, for a PUCCH, the UEmay report a number (e.g., a maximum number, in some embodiments) ofPUCCH groups supported per BWP, within a cell, and/or across CCs withina band. In some embodiments, active PUCCH resources overlapping in thetime domain may belong (or be associated with) a PUCCH group (e.g.,automatically) for intra-band. In some embodiments, active PUCCHresources overlapping in the time domain may belong (or be associatedwith) a PUCCH group for inter-band within a band group.

In some embodiments, a PUCCH group may reduce a number of beams a UE maybe required to prepare and/or track for uplink (UL) transmissions. Forexample, in some embodiments, during a UE measurement reportingprocedure, the UE may report a logic antenna panel ID used for receptionto the network. Note that the logical antenna panel ID may not berelated to a physical location of an antenna panel. In some embodiments,during the measurement reporting procedure, the UE may assign a logicalantenna panel ID to a channel state information reference signal(CSI-RS) resource indicator (CRI, e.g., which may be used to indicate apreferred beam) and/or a synchronization signal/physical broadcastchannel (SSB/PBCH) block resource indicator (SSBRI) (e.g., a resourceindex for channel state information reference signal (CSIRS) orsynchronization signal block (SSB)). In some embodiments, duringsounding reference signal (SRS) transmissions, the UE may report alogical antenna panel ID used for transmission of the SRS to thenetwork. In some embodiments, such a report (or such reporting) may beperformed separately from SRS transmissions, e.g., by mapping SRI to thelogical antenna panel ID. In some embodiments, when a base station(e.g., such as gNB 604) configures a beam for the UE via a transmissioncontrol indication (TCI), e.g., for downlink beam selection, or soundingreference indication (SRI), e.g., for uplink beam selection, the logicalantenna panel ID may be established during the measurement reportingprocedure. In other words, when the base station configures the beam forthe UE via TCI or SRI, the base station may not implicitly indicate thelogical antenna panel ID.

For example, FIG. 9 illustrates signaling between a base station and aUE to establish a beam and associated logical antenna panel ID,according to some embodiments. As shown, gNB 904 (which maybe a gNB 604)may transmit a CSI-RS/SSB 910 to UE 906 (which may be a UE 106), e.g.,as part of a beam configuration procedure. UE 906 may receive theCSI-RS/SSB 910 and perform beam measurements, including determining anantenna panel to use for communications with gNB 604. UE 906 may assigna logical antenna panel ID to the determined antenna panel and transmitbeam report 912 to gNB 904. The beam report 912 may include the logicalantenna panel ID. Upon receipt of the beam report 912, gNB 904 mayconfigure a beam and transmit beam indication 914 to UE 906. The beamindication 914 may include the logical antenna panel ID to use forcommunications.

In some embodiments, a UE may perform power management functions inwhich antenna panels may be switched into various power consumptionmodes, e.g., active and in use, active and not in use, and/or not activeand not in use. The UE, in some embodiments, may balance powerconsumption with latency. For example, in some embodiments, switching toan active antenna panel that is not in use may incur a switching delay(or latency) between 14 and 48 symbols. However, an active antenna panel(even when not in use) may consume a relatively high amount of power ascompared to a deactivated antenna panel. Additionally, in someembodiments, switching to a deactivated panel may incur a switchingdelay between 224 and 336 symbols (including activation of the antennapanel). Thus, the UE may have to balance switching latency with powerconsumption, at least in some embodiments. In some embodiments, a UE,such as UE 106, may provide (and/or update) a switching time needed foreach antenna panel to the network (e.g., to a base station, such as gNB604). In some embodiments, the update to the network may be periodicaland/or event based (e.g., when an activation/usage state of an antennapanel changes). In some embodiments, such an update (or report) may betransmitted via a PUCCH, a MAC-CE, and/or via RRC signaling. In someembodiments, each antenna panel may be assigned a logical antenna panelID and the UE may provide updates based on respective antenna panel IDs.

For example, FIG. 10 illustrates a multiple antenna panel UE switchingpanel states, according to some embodiments. As shown, a UE 1006 (whichmay be a UE 106) may include antenna panels 1020, 1022, 1024, and 1026.At a first time (t1), antenna panel 1020 may be activated and in use byUE 1006 and may have an associated switching latency (delay) of 14symbols. Additionally, UE 1006 may be operating in a power state suchthat antenna panels 1022, 1024, and 1026 may be activated. Further,antenna panels 1022, 1024, and 1026 may have an associated switchinglatency (or delay) of 28 symbols. However, at a second time (t2), whileantenna panel 1020 may remain activated and in use by UE 1006 (and mayhave an associated switching latency (delay) of 14 symbols), the UE 1006may be operating in a different power state as compared to the firsttime. Thus, antenna panel 1022 may remain activated (with, an associatedswitching latency (delay) of 28 symbols), however, antenna panels 1024and 1026 may be deactivated. Such a deactivation may cause an associatedswitching latency (delay) to increase for antenna panels 1024 and 1026to 224 symbols (as compared to 28 symbols when activated).

In some embodiments, when a base station, such as gNB 604, cannot ensurea latency requirement requested by a UE, such as UE 106, the system maybe configured to adapt in one or more ways. For example, in someembodiments, when a base station violates (and/or cannot ensure) a UEreported requirement for beam switching latency, the UE behavior may beleft to implementation (e.g., the UE may determine which beam and/orantenna panel to use without network input). As another example, in someembodiments, when a base station violates (and/or cannot ensure) a UEreported requirement for beam switching latency, the UE behavior may bepre-specified (e.g., standardized) (e.g., the UE may select a beam usedfor a control resource set (CORESET) with a lowest ID in a currentactive antenna panel and/or the UE may select a last beam used forreception and/or transmission in a current active antenna panel). As afurther example, in some embodiments, when a base station violates(and/or cannot ensure) a UE reported requirement for beam switchinglatency, the base station may indicate a logical antenna panel IDexplicitly for measurement purpose (e.g. A-CSI-RS, A-SRS). In suchinstances, there may be a restriction such that at least one beamquality for the indicated antenna panel has been reported within a timewindow. As a yet further example, in some embodiments, when a basestation violates (and/or cannot ensure) a UE reported requirement forbeam switching latency, the UE may select an antenna panel and report alogical antenna panel ID to the base station, e.g., after a beam failureand prior to the UE reporting a beam quality for an antenna panel.

In some embodiments, a pathloss measurement reference signal (RS) forSRS/PUCCH/PUSCH may be updated via a MAC CE. In such embodiments, priorto a base station (e.g., such as gNB 604) reconfiguring a pathlossmeasurement RS, the base station may confirm that a UE (such as UE 106)can measure the pathloss measurement RS at least once prior totransmission of a subsequent SRS/PUSCH/PUCCH. In some embodiments, ifthe UE cannot measure the pathloss measurement RS in time, the UE maycontinue to use a prior RS, e.g., at least until a measurement can becompleted. For example, FIG. 11 illustrates a timeline for pathlossmeasurement RS reconfiguration, according to some embodiments. As shown,a UE, such as UE 106 may receive a reference signal (RS) 1120 forpathloss measurement. The UE may then receive an RS reconfigurationindication 1122 (e.g., via a MAC CE). Further, the new RS, RS 1124, maybe received by the UE for measurement and, after a time, t1, SRS 1126may be received by the UE. However, since t1 is less than a requiredmeasurement time for the UE to measure RS 1124, the UE may continue touse RS 1120. Additionally, the UE may receive an RS reconfigurationindication 1128 (e.g., via a MAC CE) and a new RS, RS 1128, may bereceived by the UE for measurement. Further, after a time, t2, SRS 1132may be received by the UE and, since t2 is greater than the requiredmeasurement time for the UE to measure RS 1130, the UE may complete themeasurement of SRS 1132 and begin to use RS 1130.

FIG. 12 illustrates a block diagram of an example of a method for FifthGeneration New Radio (5G NR) frequency range two (FR2) basedcommunications beam management, according to some embodiments. Themethod shown in FIG. 12 may be used in conjunction with any of thesystems, methods, or devices shown in the Figures, among other devices.In various embodiments, some of the method elements shown may beperformed concurrently, in a different order than shown, or may beomitted. Additional method elements may also be performed as desired. Asshown, this method may operate as follows.

At 1202, a UE, such as UE 106, may configure, via communications with abase station, such as base station 102 and/or gNB 604, serving the UE, agroup identifier (ID) for physical uplink control channel (PUCCH)resources within a group of PUCCHs. In some embodiments, configuring thegroup ID may include comprises exchanging radio resource control (RRC)messages with the base station, e.g., during a PUCCH configurationprocedure.

At 1204, the UE may receive, from the base station serving the UE, anupdate to one or more PUCCH resources within the group of PUCCHs via amedium access control (MAC) control element (CE). In some embodiments,the MAC CE may include one of a resource ID indicating an update to aPUCCH resource or the group ID to update the group of PUCCH resources.In some embodiments, one of the resource ID, the group ID, a bandwidthpart ID, and/or a service cell ID may indicate one of a reserved valueor an invalid value. In some embodiments, when the reserved value or theinvalid value is received, the UE may assume that a single beam updatesresources, bandwidth parts, component carriers, and/or groups associatedwith the UE. In some embodiments, the UE may interpret the MAC CE as anupdate to PUCCH resources configured in a bandwidth part, an update toPUCCH resources configured in cells serving the UE, or an update toPUCCH resources configured in a cell indicated by a service cellidentifier included in the MAC CE. In some embodiments the bandwidthpart may be indicated via a bandwidth part identifier.

At 1206, the UE may update, based on the MAC-CE, the one or more PUCCHresources within the group of PUCCHs.

In some embodiments, a default PUCCH group ID may be defined and/orspecified. In some embodiments, wherein a default PUCCH group mayinclude at least one of a PUCCH group with a smallest PUCCH group ID ina current bandwidth part or a PUCCH group that includes services thatare the least delay tolerant.

In some embodiments, the UE may detect a beam failure condition anddetect, after detection of the beam failure condition, a new valid beam.In some embodiments, prior to a receiving an update from a network(e.g., the base station) indicating a new beam, the UE may switch to thenew valid beam for uplink transmissions. In some embodiments, switchingto the new valid beam for uplink transmissions may include switching tothe new beam for one or more of a physical uplink control channel(PUCCH) transmission, a sounding reference signal (SRS) transmission, aphysical uplink shared channel (PUSCH) transmission, and/or a physicalrandom-access channel (PRACH) transmission. In some embodiments,detecting the new valid beam may include the UE identifying a beamidentified during a prior candidate beam search period. In someembodiments, the UE may update a quasi co-location configuration ofPUCCH resource in a default PUCCH group using the new valid beam.

In some embodiments, the UE may activate or deactivate at least oneantenna panel used for transmissions with the base station. In suchembodiments, the UE may report, to the base station, capabilitiesassociated with a quasi co-location (QCL) update. The capabilities mayinclude at least one of, one or more of, and/or both of a number (e.g.,a maximum number, in some embodiments) of supported transmissionconfiguration indicator (TCI) states across component careers (CCs)within a band or a number (e.g., a maximum number, in some embodiments)of PUCCH groups supported per BWP, within a cell, or across CCs within aband for a PUCCH. In some embodiments, active PUCCH resources fromdifferent component carriers overlapping in the time domain may beassociated with a PUCCH group for intra-band carrier aggregation orinter-band carrier aggregation.

In some embodiments, the UE may assign, during a measurement reportingprocedure, a logical antenna panel ID to a channel state informationreference signal (CSI-RS) resource indicator (CRI) or a synchronizationsignal/physical broadcast channel (SSB/PBCH) block resource indicator(SSBRI). In such embodiments, the UE may report, during the measurementreporting procedure, the logical antenna panel ID used for transmissionto and/or reception from the base station. In some embodiments, theCM/SSBRI may indicate a preferred beam. In some embodiments, theCRI/SSBRI may be a resource index for channel state informationreference signal (CSIRS) or synchronization signal block (SSB)). In someembodiments, the UE may report, during sounding reference signal (SRS)transmissions, a logical antenna panel ID used for SRS transmissions.

In some embodiments, the UE may provide, to the base station, anindication of an antenna panel switching time via one of a MAC-CE, radioresource control (RRC) signaling, or signaling via a PUCCH. In someembodiments, the indication may be on a per antenna panel basis. In someembodiments, antenna panels may be identified via logical antenna panelidentifiers (IDs). In some embodiments, the indication may be providedperiodically to the base station. In some embodiments, the indicationmay be provided a-periodically to the base station, e.g., when UEdecides to change a panel power management state. In some embodiments,the indication may be provided to the base station based on anoccurrence of an event. In such embodiments, the event may include atleast one of activation of an antenna panel, deactivation of an antennapanel, and/or switching to or from an antenna panel fortransmission/reception.

In some embodiments, the UE may report, to the base station, a minimumlatency requirement for switching antenna panels. In some embodiments,in response to the base station violating the minimum latencyrequirement, the UE may determine an antenna panel to use without inputfrom the base station. In some embodiments, in response to the basestation violating the minimum latency requirement, the UE may determinean antenna panel to use based on a pre-specified configuration. In suchembodiments, the pre-specified configuration may include one of the UEselecting a beam used for a control resource set (CORESET) with a lowestID in a current active antenna panel and/or the UE selecting a last beamused for reception and/or transmission in a current active antennapanel. In some embodiments, in response to the base station violatingthe minimum latency requirement, the UE may receive, from the basestation, an indication of a logical antenna panel ID to use formeasurements. In some embodiments, the report may be provided via one ofa MAC-CE, radio resource control (RRC) signaling, or signaling via aPUCCH.

In some embodiments, the UE may receive, from the base station, anupdate to a pathloss measurement reference signal (RS) via a MAC CE. Insome embodiments, when (if) the UE cannot (reliably) measure thepathloss measurement RS (e.g., at least once) prior to transmission of asubsequent sounding reference signal/physical uplink sharedchannel/PUCCH (SRS/PUSCH/PUCCH), the UE may continue to use pathlossestimate from a prior RS to determine the uplink open loop transmitpower until pathloss can be (reliably) measured from the new pathlossmeasurement RS.

FIG. 13 illustrates a block diagram of another example of a method forFifth Generation New Radio (5G NR) frequency range two (FR2) basedcommunications beam management, according to some embodiments. Themethod shown in FIG. 13 may be used in conjunction with any of thesystems, methods, or devices shown in the Figures, among other devices.In various embodiments, some of the method elements shown may beperformed concurrently, in a different order than shown, or may beomitted. Additional method elements may also be performed as desired. Asshown, this method may operate as follows.

At 1302, a UE, such as UE 106, may activate and/or deactivate at leastone antenna panel used for communications with a base station, such asbase station 102 and/or gNB 604, serving the UE.

At 1304, the UE may report, to the base station, capabilities associatedwith a quasi co-location (QCL) update. The capabilities may include atleast one of, one or more of, and/or both of a number (e.g., a maximumnumber, in some embodiments) of supported transmission configurationindicator (TCI) states across component careers (CCs) within a band or anumber (e.g., a maximum number, in some embodiments) of PUCCH groupssupported per BWP, within a cell, or across CCs within a band for aPUCCH. In some embodiments, active PUCCH resources from differentcomponent carriers overlapping in the time domain may be associated witha PUCCH group for intra-band carrier aggregation or inter-band carrieraggregation.

In some embodiments, the UE may configure, via communications with thebase station serving the UE, a group identifier (ID) for physical uplinkcontrol channel (PUCCH) resources within a group of PUCCHs. In someembodiments, configuring the group ID may include comprises exchangingradio resource control (RRC) messages with the base station, e.g.,during a PUCCH configuration procedure. Additionally, the UE mayreceive, from the base station serving the UE, an update to one or morePUCCH resources within the group of PUCCHs via a medium access control(MAC) control element (CE). In some embodiments, the MAC CE may includeone of a resource ID indicating an update to a PUCCH resource or thegroup ID to update the group of PUCCH resources. In some embodiments,one of the resource ID, the group ID, a bandwidth part ID, and/or aservice cell ID may indicate one of a reserved value or an invalidvalue. In some embodiments, when the reserved value or the invalid valueis received, the UE may assume that a single beam updates resources,bandwidth parts, component carriers, and/or groups associated with theUE. In some embodiments, the UE may interpret the MAC CE as an update toPUCCH resources configured in a bandwidth part, an update to PUCCHresources configured in cells serving the UE, or an update to PUCCHresources configured in a cell indicated by a service cell identifierincluded in the MAC CE. In some embodiments the bandwidth part may beindicated via a bandwidth part identifier. In some embodiments, the UEmay update, based on the MAC-CE, the one or more PUCCH resources withinthe group of PUCCHs.

In some embodiments, a default PUCCH group ID may be defined and/orspecified. In some embodiments, wherein a default PUCCH group mayinclude at least one of a PUCCH group with a smallest PUCCH group ID ina current bandwidth part or a PUCCH group that includes services thatare the least delay tolerant.

In some embodiments, the UE may detect a beam failure condition anddetect, after detection of the beam failure condition, a new valid beam.In some embodiments, prior to a receiving an update from a network(e.g., the base station) indicating a new beam, the UE may switch to thenew valid beam for uplink transmissions. In some embodiments, switchingto the new valid beam for uplink transmissions may include switching tothe new beam for one or more of a physical uplink control channel(PUCCH) transmission, a sounding reference signal (SRS) transmission, aphysical uplink shared channel (PUSCH) transmission, and/or a physicalrandom-access channel (PRACH) transmission. In some embodiments,detecting the new valid beam may include the UE identifying a beamidentified during a prior candidate beam search period. In someembodiments, the UE may update a quasi co-location configuration ofPUCCH resource in a default PUCCH group using the new valid beam. Insome embodiments, the UE may update a quasi co-location configuration ofPUCCH resource in a default PUCCH group using the new valid beam. Insome embodiments, the UE may update a quasi co-location configuration ofPUCCH resource in a default PUCCH group using the new valid beam.

In some embodiments, the UE may assign, during a measurement reportingprocedure, a logical antenna panel ID to a channel state informationreference signal (CSI-RS) resource indicator (CRI) or a synchronizationsignal/physical broadcast channel (SSB/PBCH) block resource indicator(SSBRI). In such embodiments, the UE may report, during the measurementreporting procedure, the logical antenna panel ID used for transmissionto and/or reception from the base station. In some embodiments, theCM/SSBRI may indicate a preferred beam. In some embodiments, theCRI/SSBRI may be a resource index for channel state informationreference signal (CSIRS) or synchronization signal block (SSB)). In someembodiments, the UE may report, during sounding reference signal (SRS)transmissions, a logical antenna panel ID used for SRS transmissions.

In some embodiments, the UE may provide, to the base station, anindication of an antenna panel switching time via one of a MAC-CE, radioresource control (RRC) signaling, or signaling via a PUCCH. In someembodiments, the indication may be on a per antenna panel basis. In someembodiments, antenna panels may be identified via logical antenna panelidentifiers (IDs). In some embodiments, the indication may be providedperiodically to the base station. In some embodiments, the indicationmay be provided a-periodically to the base station, e.g., when UEdecides to change a panel power management state. In some embodiments,the indication may be provided to the base station based on anoccurrence of an event. In such embodiments, the event may include atleast one of activation of an antenna panel, deactivation of an antennapanel, and/or switching to or from an antenna panel fortransmission/reception.

In some embodiments, the UE may report, to the base station, a minimumlatency requirement for switching antenna panels. In some embodiments,in response to the base station violating the minimum latencyrequirement, the UE may determine an antenna panel to use without inputfrom the base station. In some embodiments, in response to the basestation violating the minimum latency requirement, the UE may determinean antenna panel to use based on a pre-specified configuration. In suchembodiments, the pre-specified configuration may include one of the UEselecting a beam used for a control resource set (CORESET) with a lowestID in a current active antenna panel and/or the UE selecting a last beamused for reception and/or transmission in a current active antennapanel. In some embodiments, in response to the base station violatingthe minimum latency requirement, the UE may receive, from the basestation, an indication of a logical antenna panel ID to use formeasurements. In some embodiments, the report may be provided via one ofa MAC-CE, radio resource control (RRC) signaling, or signaling via aPUCCH.

In some embodiments, the UE may receive, from the base station, anupdate to a pathloss measurement reference signal (RS) via a MAC CE. Insome embodiments, when (if) the UE cannot (reliably) measure thepathloss measurement RS (e.g., at least once) prior to transmission of asubsequent sounding reference signal/physical uplink sharedchannel/PUCCH (SRS/PUSCH/PUCCH), the UE may continue to use pathlossestimate from a prior RS to determine the uplink open loop transmitpower until pathloss can be (reliably) measured from the new pathlossmeasurement RS.

FIG. 14 illustrates a block diagram of another example of a method forFifth Generation New Radio (5G NR) frequency range two (FR2) basedcommunications beam management, according to some embodiments. Themethod shown in FIG. 14 may be used in conjunction with any of thesystems, methods, or devices shown in the Figures, among other devices.In various embodiments, some of the method elements shown may beperformed concurrently, in a different order than shown, or may beomitted. Additional method elements may also be performed as desired. Asshown, this method may operate as follows.

At 1402, a UE, such as UE 106, may assign, during a measurementreporting procedure with a base station, such as base station 102 and/orgNB 604, serving the UE, a logical antenna panel ID to a channel stateinformation reference signal (CSI-RS) resource indicator (CRI) or asynchronization signal/physical broadcast channel (SSB/PBCH) blockresource indicator (SSBRI).

At 1404, the UE may report, during the measurement reporting procedure,the logical antenna panel ID used for transmission to and/or receptionfrom the base station. In some embodiments, the CRI/SSBRI may indicate apreferred beam. In some embodiments, the CRI/SSBRI may be a resourceindex for channel state information reference signal (CSIRS) orsynchronization signal block (SSB)). In some embodiments, the UE mayreport, during sounding reference signal (SRS) transmissions, a logicalantenna panel ID used for SRS transmissions.

In some embodiments, the UE may configure, via communications with thebase station serving the UE, a group identifier (ID) for physical uplinkcontrol channel (PUCCH) resources within a group of PUCCHs. In someembodiments, configuring the group ID may include comprises exchangingradio resource control (RRC) messages with the base station, e.g.,during a PUCCH configuration procedure. Additionally, the UE mayreceive, from the base station serving the UE, an update to one or morePUCCH resources within the group of PUCCHs via a medium access control(MAC) control element (CE). In some embodiments, the MAC CE may includeone of a resource ID indicating an update to a PUCCH resource or thegroup ID to update the group of PUCCH resources. In some embodiments,one of the resource ID, the group ID, a bandwidth part ID, and/or aservice cell ID may indicate one of a reserved value or an invalidvalue. In some embodiments, when the reserved value or the invalid valueis received, the UE may assume that a single beam updates resources,bandwidth parts, component carriers, and/or groups associated with theUE. In some embodiments, the UE may interpret the MAC CE as an update toPUCCH resources configured in a bandwidth part, an update to PUCCHresources configured in cells serving the UE, or an update to PUCCHresources configured in a cell indicated by a service cell identifierincluded in the MAC CE. In some embodiments the bandwidth part may beindicated via a bandwidth part identifier. In some embodiments, the UEmay update, based on the MAC-CE, the one or more PUCCH resources withinthe group of PUCCHs.

In some embodiments, a default PUCCH group ID may be defined and/orspecified. In some embodiments, wherein a default PUCCH group mayinclude at least one of a PUCCH group with a smallest PUCCH group ID ina current bandwidth part or a PUCCH group that includes services thatare the least delay tolerant.

In some embodiments, the UE may detect a beam failure condition anddetect, after detection of the beam failure condition, a new valid beam.In some embodiments, prior to a receiving an update from a network(e.g., the base station) indicating a new beam, the UE may switch to thenew valid beam for uplink transmissions. In some embodiments, switchingto the new valid beam for uplink transmissions may include switching tothe new beam for one or more of a physical uplink control channel(PUCCH) transmission, a sounding reference signal (SRS) transmission, aphysical uplink shared channel (PUSCH) transmission, and/or a physicalrandom-access channel (PRACH) transmission. In some embodiments,detecting the new valid beam may include the UE identifying a beamidentified during a prior candidate beam search period. In someembodiments, the UE may update a quasi co-location configuration ofPUCCH resource in a default PUCCH group using the new valid beam.

In some embodiments, the UE may activate or deactivate at least oneantenna panel used for transmissions with the base station. In suchembodiments, the UE may report, to the base station, capabilitiesassociated with a quasi co-location (QCL) update. The capabilities mayinclude at least one of, one or more of, and/or both of a number (e.g.,a maximum number, in some embodiments) of supported transmissionconfiguration indicator (TCI) states across component careers (CCs)within a band or a number (e.g., a maximum number, in some embodiments)of PUCCH groups supported per BWP, within a cell, or across CCs within aband for a PUCCH. In some embodiments, active PUCCH resources fromdifferent component carriers overlapping in the time domain may beassociated with a PUCCH group for intra-band carrier aggregation orinter-band carrier aggregation.

In some embodiments, the UE may provide, to the base station, anindication of an antenna panel switching time via one of a MAC-CE, radioresource control (RRC) signaling, or signaling via a PUCCH. In someembodiments, the indication may be on a per antenna panel basis. In someembodiments, antenna panels may be identified via logical antenna panelidentifiers (IDs). In some embodiments, the indication may be providedperiodically to the base station. In some embodiments, the indicationmay be provided a-periodically to the base station, e.g., when UEdecides to change a panel power management state. In some embodiments,the indication may be provided to the base station based on anoccurrence of an event. In such embodiments, the event may include atleast one of activation of an antenna panel, deactivation of an antennapanel, and/or switching to or from an antenna panel fortransmission/reception.

In some embodiments, the UE may report, to the base station, a minimumlatency requirement for switching antenna panels. In some embodiments,in response to the base station violating the minimum latencyrequirement, the UE may determine an antenna panel to use without inputfrom the base station. In some embodiments, in response to the basestation violating the minimum latency requirement, the UE may determinean antenna panel to use based on a pre-specified configuration. In suchembodiments, the pre-specified configuration may include one of the UEselecting a beam used for a control resource set (CORESET) with a lowestID in a current active antenna panel and/or the UE selecting a last beamused for reception and/or transmission in a current active antennapanel. In some embodiments, in response to the base station violatingthe minimum latency requirement, the UE may receive, from the basestation, an indication of a logical antenna panel ID to use formeasurements. In some embodiments, the report may be provided via one ofa MAC-CE, radio resource control (RRC) signaling, or signaling via aPUCCH.

In some embodiments, the UE may receive, from the base station, anupdate to a pathloss measurement reference signal (RS) via a MAC CE. Insome embodiments, when (if) the UE cannot (reliably) measure thepathloss measurement RS (e.g., at least once) prior to transmission of asubsequent sounding reference signal/physical uplink sharedchannel/PUCCH (SRS/PUSCH/PUCCH), the UE may continue to use pathlossestimate from a prior RS to determine the uplink open loop transmitpower until pathloss can be (reliably) measured from the new pathlossmeasurement RS.

FIG. 15 illustrates a block diagram of another example of a method forFifth Generation New Radio (5G NR) frequency range two (FR2) basedcommunications beam management, according to some embodiments. Themethod shown in FIG. 15 may be used in conjunction with any of thesystems, methods, or devices shown in the Figures, among other devices.In various embodiments, some of the method elements shown may beperformed concurrently, in a different order than shown, or may beomitted. Additional method elements may also be performed as desired. Asshown, this method may operate as follows.

At 1502, a UE, such as UE 106, may attach to a base station, such asbase station 102 and/or gNB 604. In some embodiments, the attachment mayinclude exchange of one or more configuration messages.

At 1504, the UE may provide, to the base station, an indication of anantenna panel switching time. In some embodiments, the indication may beprovided via one of a MAC-CE, radio resource control (RRC) signaling, orsignaling via a PUCCH.

In some embodiments, the indication may be on a per antenna panel basis.In some embodiments, antenna panels may be identified via logicalantenna panel identifiers (IDs). In some embodiments, the indication maybe provided periodically to the base station. In some embodiments, theindication may be provided to the base station based on an occurrence ofan event. In such embodiments, the event may include at least one ofactivation of an antenna panel, deactivation of an antenna panel, and/orswitching to or from an antenna panel for transmission/reception.

In some embodiments, the UE may configure, via communications with thebase station serving the UE, a group identifier (ID) for physical uplinkcontrol channel (PUCCH) resources within a group of PUCCHs. In someembodiments, configuring the group ID may include comprises exchangingradio resource control (RRC) messages with the base station, e.g.,during a PUCCH configuration procedure. Additionally, the UE mayreceive, from the base station serving the UE, an update to one or morePUCCH resources within the group of PUCCHs via a medium access control(MAC) control element (CE). In some embodiments, the MAC CE may includeone of a resource ID indicating an update to a PUCCH resource or thegroup ID to update the group of PUCCH resources. In some embodiments,one of the resource ID, the group ID, a bandwidth part ID, and/or aservice cell ID may indicate one of a reserved value or an invalidvalue. In some embodiments, when the reserved value or the invalid valueis received, the UE may assume that a single beam updates resources,bandwidth parts, component carriers, and/or groups associated with theUE. In some embodiments, the UE may interpret the MAC CE as an update toPUCCH resources configured in a bandwidth part, an update to PUCCHresources configured in cells serving the UE, or an update to PUCCHresources configured in a cell indicated by a service cell identifierincluded in the MAC CE. In some embodiments the bandwidth part may beindicated via a bandwidth part identifier. In some embodiments, the UEmay update, based on the MAC-CE, the one or more PUCCH resources withinthe group of PUCCHs.

In some embodiments, a default PUCCH group ID may be defined and/orspecified. In some embodiments, wherein a default PUCCH group mayinclude at least one of a PUCCH group with a smallest PUCCH group ID ina current bandwidth part or a PUCCH group that includes services thatare the least delay tolerant.

In some embodiments, the UE may detect a beam failure condition anddetect, after detection of the beam failure condition, a new valid beam.In some embodiments, prior to a receiving an update from a network(e.g., the base station) indicating a new beam, the UE may switch to thenew valid beam for uplink transmissions. In some embodiments, switchingto the new valid beam for uplink transmissions may include switching tothe new beam for one or more of a physical uplink control channel(PUCCH) transmission, a sounding reference signal (SRS) transmission, aphysical uplink shared channel (PUSCH) transmission, and/or a physicalrandom-access channel (PRACH) transmission. In some embodiments,detecting the new valid beam may include the UE identifying a beamidentified during a prior candidate beam search period. In someembodiments, the UE may update a quasi co-location configuration ofPUCCH resource in a default PUCCH group using the new valid beam.

In some embodiments, the UE may activate or deactivate at least oneantenna panel used for transmissions with the base station. In suchembodiments, the UE may report, to the base station, capabilitiesassociated with a quasi co-location (QCL) update. The capabilities mayinclude at least one of, one or more of, and/or both of a number (e.g.,a maximum number, in some embodiments) of supported transmissionconfiguration indicator (TCI) states across component careers (CCs)within a band or a number (e.g., a maximum number, in some embodiments)of PUCCH groups supported per BWP, within a cell, or across CCs within aband for a PUCCH. In some embodiments, active PUCCH resources fromdifferent component carriers overlapping in the time domain may beassociated with a PUCCH group for intra-band carrier aggregation orinter-band carrier aggregation.

In some embodiments, the UE may assign, during a measurement reportingprocedure, a logical antenna panel ID to a channel state informationreference signal (CSI-RS) resource indicator (CRI) or a synchronizationsignal/physical broadcast channel (SSB/PBCH) block resource indicator(SSBRI). In such embodiments, the UE may report, during the measurementreporting procedure, the logical antenna panel ID used for transmissionto and/or reception from the base station. In some embodiments, theCRI/SSBRI may indicate a preferred beam. In some embodiments, theCRI/SSBRI may be a resource index for channel state informationreference signal (CSIRS) or synchronization signal block (SSB)). In someembodiments, the UE may report, during sounding reference signal (SRS)transmissions, a logical antenna panel ID used for SRS transmissions.

In some embodiments, the UE may report, to the base station, a minimumlatency requirement for switching antenna panels. In some embodiments,in response to the base station violating the minimum latencyrequirement, the UE may determine an antenna panel to use without inputfrom the base station. In some embodiments, in response to the basestation violating the minimum latency requirement, the UE may determinean antenna panel to use based on a pre-specified configuration. In suchembodiments, the pre-specified configuration may include one of the UEselecting a beam used for a control resource set (CORESET) with a lowestID in a current active antenna panel and/or the UE selecting a last beamused for reception and/or transmission in a current active antennapanel. In some embodiments, in response to the base station violatingthe minimum latency requirement, the UE may receive, from the basestation, an indication of a logical antenna panel ID to use formeasurements. In some embodiments, the report may be provided via one ofa MAC-CE, radio resource control (RRC) signaling, or signaling via aPUCCH.

In some embodiments, the UE may receive, from the base station, anupdate to a pathloss measurement reference signal (RS) via a MAC CE. Insome embodiments, when (if) the UE cannot (reliably) measure thepathloss measurement RS (e.g., at least once) prior to transmission of asubsequent sounding reference signal/physical uplink sharedchannel/PUCCH (SRS/PUSCH/PUCCH), the UE may continue to use pathlossestimate from a prior RS to determine the uplink open loop transmitpower until pathloss can be (reliably) measured from the new pathlossmeasurement RS.

FIG. 16 illustrates a block diagram of another example of a method forFifth Generation New Radio (5G NR) frequency range two (FR2) basedcommunications beam management, according to some embodiments. Themethod shown in FIG. 16 may be used in conjunction with any of thesystems, methods, or devices shown in the Figures, among other devices.In various embodiments, some of the method elements shown may beperformed concurrently, in a different order than shown, or may beomitted. Additional method elements may also be performed as desired. Asshown, this method may operate as follows.

At 1602, a UE, such as UE 106, may report, to the base station, such asbase station 102 and/or gNB 604, serving the UE, a minimum latencyrequirement for switching antenna panels.

At 1604, the UE may, in response to the base station violating theminimum latency requirement, determine an antenna panel to use withoutinput from the base station. In some embodiments, in response to thebase station violating the minimum latency requirement, the UE maydetermine an antenna panel to use based on a pre-specifiedconfiguration. In such embodiments, the pre-specified configuration mayinclude one of the UE selecting a beam used for a control resource set(CORESET) with a lowest ID in a current active antenna panel and/or theUE selecting a last beam used for reception and/or transmission in acurrent active antenna panel. In some embodiments, in response to thebase station violating the minimum latency requirement, the UE mayreceive, from the base station, an indication of a logical antenna panelID to use for measurements. In some embodiments, the report may beprovided via one of a MAC-CE, radio resource control (RRC) signaling, orsignaling via a PUCCH.

In some embodiments, the UE may configure, via communications with thebase station serving the UE, a group identifier (ID) for physical uplinkcontrol channel (PUCCH) resources within a group of PUCCHs. In someembodiments, configuring the group ID may include comprises exchangingradio resource control (RRC) messages with the base station, e.g.,during a PUCCH configuration procedure. Additionally, the UE mayreceive, from the base station serving the UE, an update to one or morePUCCH resources within the group of PUCCHs via a medium access control(MAC) control element (CE). In some embodiments, the MAC CE may includeone of a resource ID indicating an update to a PUCCH resource or thegroup ID to update the group of PUCCH resources. In some embodiments,one of the resource ID, the group ID, a bandwidth part ID, and/or aservice cell ID may indicate one of a reserved value or an invalidvalue. In some embodiments, when the reserved value or the invalid valueis received, the UE may assume that a single beam updates resources,bandwidth parts, component carriers, and/or groups associated with theUE. In some embodiments, the UE may interpret the MAC CE as an update toPUCCH resources configured in a bandwidth part, an update to PUCCHresources configured in cells serving the UE, or an update to PUCCHresources configured in a cell indicated by a service cell identifierincluded in the MAC CE. In some embodiments the bandwidth part may beindicated via a bandwidth part identifier. In some embodiments, the UEmay update, based on the MAC-CE, the one or more PUCCH resources withinthe group of PUCCHs.

In some embodiments, a default PUCCH group ID may be defined and/orspecified. In some embodiments, wherein a default PUCCH group mayinclude at least one of a PUCCH group with a smallest PUCCH group ID ina current bandwidth part or a PUCCH group that includes services thatare the least delay tolerant.

In some embodiments, the UE may detect a beam failure condition anddetect, after detection of the beam failure condition, a new valid beam.In some embodiments, prior to a receiving an update from a network(e.g., the base station) indicating a new beam, the UE may switch to thenew valid beam for uplink transmissions. In some embodiments, switchingto the new valid beam for uplink transmissions may include switching tothe new beam for one or more of a physical uplink control channel(PUCCH) transmission, a sounding reference signal (SRS) transmission, aphysical uplink shared channel (PUSCH) transmission, and/or a physicalrandom-access channel (PRACH) transmission. In some embodiments,detecting the new valid beam may include the UE identifying a beamidentified during a prior candidate beam search period. In someembodiments, the UE may update a quasi co-location configuration ofPUCCH resource in a default PUCCH group using the new valid beam.

In some embodiments, the UE may activate or deactivate at least oneantenna panel used for transmissions with the base station. In suchembodiments, the UE may report, to the base station, capabilitiesassociated with a quasi co-location (QCL) update. The capabilities mayinclude at least one of, one or more of, and/or both of a number (e.g.,a maximum number, in some embodiments) of supported transmissionconfiguration indicator (TCI) states across component careers (CCs)within a band or a number (e.g., a maximum number, in some embodiments)of PUCCH groups supported per BWP, within a cell, or across CCs within aband for a PUCCH. In some embodiments, active PUCCH resources fromdifferent component carriers overlapping in the time domain may beassociated with a PUCCH group for intra-band carrier aggregation orinter-band carrier aggregation.

In some embodiments, the UE may assign, during a measurement reportingprocedure, a logical antenna panel ID to a channel state informationreference signal (CSI-RS) resource indicator (CRI) or a synchronizationsignal/physical broadcast channel (SSB/PBCH) block resource indicator(SSBRI). In such embodiments, the UE may report, during the measurementreporting procedure, the logical antenna panel ID used for transmissionto and/or reception from the base station. In some embodiments, theCM/SSBRI may indicate a preferred beam. In some embodiments, theCRI/SSBRI may be a resource index for channel state informationreference signal (CSIRS) or synchronization signal block (SSB)). In someembodiments, the UE may report, during sounding reference signal (SRS)transmissions, a logical antenna panel ID used for SRS transmissions.

In some embodiments, the UE may provide, to the base station, anindication of an antenna panel switching time via one of a MAC-CE, radioresource control (RRC) signaling, or signaling via a PUCCH. In someembodiments, the indication may be on a per antenna panel basis. In someembodiments, antenna panels may be identified via logical antenna panelidentifiers (IDs). In some embodiments, the indication may be providedperiodically to the base station. In some embodiments, the indicationmay be provided a-periodically to the base station, e.g., when UEdecides to change a panel power management state. In some embodiments,the indication may be provided to the base station based on anoccurrence of an event. In such embodiments, the event may include atleast one of activation of an antenna panel, deactivation of an antennapanel, and/or switching to or from an antenna panel fortransmission/reception.

In some embodiments, the UE may receive, from the base station, anupdate to a pathloss measurement reference signal (RS) via a MAC CE. Insome embodiments, when (if) the UE cannot (reliably) measure thepathloss measurement RS (e.g., at least once) prior to transmission of asubsequent sounding reference signal/physical uplink sharedchannel/PUCCH (SRS/PUSCH/PUCCH), the UE may continue to use pathlossestimate from a prior RS to determine the uplink open loop transmitpower until pathloss can be (reliably) measured from the new pathlossmeasurement RS.

FIG. 17 illustrates a block diagram of another example of a method forFifth Generation New Radio (5G NR) frequency range two (FR2) basedcommunications beam management, according to some embodiments. Themethod shown in FIG. 17 may be used in conjunction with any of thesystems, methods, or devices shown in the Figures, among other devices.In various embodiments, some of the method elements shown may beperformed concurrently, in a different order than shown, or may beomitted. Additional method elements may also be performed as desired. Asshown, this method may operate as follows.

At 1702, a UE, such as UE 106, may attach to a base station, such asbase station 102 and/or gNB 604. In some embodiments, the attachment mayinclude exchange of one or more configuration messages.

At 1704, the UE may receive, from the base station, an update to apathloss measurement reference signal (RS) via a MAC CE. In someembodiments, when (if) the UE cannot (reliably) measure the pathlossmeasurement RS (e.g., at least once) prior to transmission of asubsequent sounding reference signal/physical uplink sharedchannel/PUCCH (SRS/PUSCH/PUCCH), the UE may continue to use pathlossestimate from a prior RS to determine the uplink open loop transmitpower until pathloss can be (reliably) measured from the new pathlossmeasurement RS.

In some embodiments, the UE may configure, via communications with thebase station serving the UE, a group identifier (ID) for physical uplinkcontrol channel (PUCCH) resources within a group of PUCCHs. In someembodiments, configuring the group ID may include comprises exchangingradio resource control (RRC) messages with the base station, e.g.,during a PUCCH configuration procedure. Additionally, the UE mayreceive, from the base station serving the UE, an update to one or morePUCCH resources within the group of PUCCHs via a medium access control(MAC) control element (CE). In some embodiments, the MAC CE may includeone of a resource ID indicating an update to a PUCCH resource or thegroup ID to update the group of PUCCH resources. In some embodiments,one of the resource ID, the group ID, a bandwidth part ID, and/or aservice cell ID may indicate one of a reserved value or an invalidvalue. In some embodiments, when the reserved value or the invalid valueis received, the UE may assume that a single beam updates resources,bandwidth parts, component carriers, and/or groups associated with theUE. In some embodiments, the UE may interpret the MAC CE as an update toPUCCH resources configured in a bandwidth part, an update to PUCCHresources configured in cells serving the UE, or an update to PUCCHresources configured in a cell indicated by a service cell identifierincluded in the MAC CE. In some embodiments the bandwidth part may beindicated via a bandwidth part identifier. In some embodiments, the UEmay update, based on the MAC-CE, the one or more PUCCH resources withinthe group of PUCCHs.

In some embodiments, a default PUCCH group ID may be defined and/orspecified. In some embodiments, wherein a default PUCCH group mayinclude at least one of a PUCCH group with a smallest PUCCH group ID ina current bandwidth part or a PUCCH group that includes services thatare the least delay tolerant.

In some embodiments, the UE may detect a beam failure condition anddetect, after detection of the beam failure condition, a new valid beam.In some embodiments, prior to a receiving an update from a network(e.g., the base station) indicating a new beam, the UE may switch to thenew valid beam for uplink transmissions. In some embodiments, switchingto the new valid beam for uplink transmissions may include switching tothe new beam for one or more of a physical uplink control channel(PUCCH) transmission, a sounding reference signal (SRS) transmission, aphysical uplink shared channel (PUSCH) transmission, and/or a physicalrandom-access channel (PRACH) transmission. In some embodiments,detecting the new valid beam may include the UE identifying a beamidentified during a prior candidate beam search period. In someembodiments, the UE may update a quasi co-location configuration ofPUCCH resource in a default PUCCH group using the new valid beam.

In some embodiments, the UE may activate or deactivate at least oneantenna panel used for transmissions with the base station. In suchembodiments, the UE may report, to the base station, capabilitiesassociated with a quasi co-location (QCL) update. The capabilities mayinclude at least one of, one or more of, and/or both of a number (e.g.,a maximum number, in some embodiments) of supported transmissionconfiguration indicator (TCI) states across component careers (CCs)within a band or a number (e.g., a maximum number, in some embodiments)of PUCCH groups supported per BWP, within a cell, or across CCs within aband for a PUCCH. In some embodiments, active PUCCH resources fromdifferent component carriers overlapping in the time domain may beassociated with a PUCCH group for intra-band carrier aggregation orinter-band carrier aggregation.

In some embodiments, the UE may assign, during a measurement reportingprocedure, a logical antenna panel ID to a channel state informationreference signal (CSI-RS) resource indicator (CRI) or a synchronizationsignal/physical broadcast channel (SSB/PBCH) block resource indicator(SSBRI). In such embodiments, the UE may report, during the measurementreporting procedure, the logical antenna panel ID used for transmissionto and/or reception from the base station. In some embodiments, theCM/SSBRI may indicate a preferred beam. In some embodiments, theCRI/SSBRI may be a resource index for channel state informationreference signal (CSIRS) or synchronization signal block (SSB)). In someembodiments, the UE may report, during sounding reference signal (SRS)transmissions, a logical antenna panel ID used for SRS transmissions.

In some embodiments, the UE may provide, to the base station, anindication of an antenna panel switching time via one of a MAC-CE, radioresource control (RRC) signaling, or signaling via a PUCCH. In someembodiments, the indication may be on a per antenna panel basis. In someembodiments, antenna panels may be identified via logical antenna panelidentifiers (IDs). In some embodiments, the indication may be providedperiodically to the base station. In some embodiments, the indicationmay be provided a-periodically to the base station, e.g., when UEdecides to change a panel power management state. In some embodiments,the indication may be provided to the base station based on anoccurrence of an event. In such embodiments, the event may include atleast one of activation of an antenna panel, deactivation of an antennapanel, and/or switching to or from an antenna panel fortransmission/reception.

In some embodiments, the UE may report, to the base station, a minimumlatency requirement for switching antenna panels. In some embodiments,in response to the base station violating the minimum latencyrequirement, the UE may determine an antenna panel to use without inputfrom the base station. In some embodiments, in response to the basestation violating the minimum latency requirement, the UE may determinean antenna panel to use based on a pre-specified configuration. In suchembodiments, the pre-specified configuration may include one of the UEselecting a beam used for a control resource set (CORESET) with a lowestID in a current active antenna panel and/or the UE selecting a last beamused for reception and/or transmission in a current active antennapanel. In some embodiments, in response to the base station violatingthe minimum latency requirement, the UE may receive, from the basestation, an indication of a logical antenna panel ID to use formeasurements. In some embodiments, the report may be provided via one ofa MAC-CE, radio resource control (RRC) signaling, or signaling via aPUCCH.

FIG. 18 illustrates a block diagram of another example of a method forFifth Generation New Radio (5G NR) frequency range two (FR2) basedcommunications beam management, according to some embodiments. Themethod shown in FIG. 18 may be used in conjunction with any of thesystems, methods, or devices shown in the Figures, among other devices.In various embodiments, some of the method elements shown may beperformed concurrently, in a different order than shown, or may beomitted. Additional method elements may also be performed as desired. Asshown, this method may operate as follows.

At 1802, a UE, such as UE 106, may detect a beam failure condition. Insome embodiments, prior to detection of the beam failure conditions, theUE may attach to a base station, such as base station 102 and/or gNB604. In some embodiments, the attachment may include exchange of one ormore configuration messages.

At 1804, the UE may, responsive to (and/or after) detection of the beamfailure condition, detect a new valid beam. In some embodiments,detecting the new valid beam may include the UE identifying a beamidentified during a prior candidate beam search period. In someembodiments, the UE may update a quasi co-location configuration ofPUCCH resource in a default PUCCH group using the new valid beam.

At 1806, prior to a receiving an update from a network (e.g., the basestation) indicating a new beam, the UE may switch to the new valid beamfor uplink transmissions. In some embodiments, switching to the newvalid beam for uplink transmissions may include switching to the newbeam for one or more of a physical uplink control channel (PUCCH)transmission, a sounding reference signal (SRS) transmission, a physicaluplink shared channel (PUSCH) transmission, and/or a physicalrandom-access channel (PRACH) transmission.

In some embodiments, the UE may configure, via communications with thebase station serving the UE, a group identifier (ID) for physical uplinkcontrol channel (PUCCH) resources within a group of PUCCHs. In someembodiments, configuring the group ID may include comprises exchangingradio resource control (RRC) messages with the base station, e.g.,during a PUCCH configuration procedure. Additionally, the UE mayreceive, from the base station serving the UE, an update to one or morePUCCH resources within the group of PUCCHs via a medium access control(MAC) control element (CE). In some embodiments, the MAC CE may includeone of a resource ID indicating an update to a PUCCH resource or thegroup ID to update the group of PUCCH resources. In some embodiments,one of the resource ID, the group ID, a bandwidth part ID, and/or aservice cell ID may indicate one of a reserved value or an invalidvalue. In some embodiments, when the reserved value or the invalid valueis received, the UE may assume that a single beam updates resources,bandwidth parts, component carriers, and/or groups associated with theUE. In some embodiments, the UE may interpret the MAC CE as an update toPUCCH resources configured in a bandwidth part, an update to PUCCHresources configured in cells serving the UE, or an update to PUCCHresources configured in a cell indicated by a service cell identifierincluded in the MAC CE. In some embodiments the bandwidth part may beindicated via a bandwidth part identifier. In some embodiments, the UEmay update, based on the MAC-CE, the one or more PUCCH resources withinthe group of PUCCHs.

In some embodiments, a default PUCCH group ID may be defined and/orspecified. In some embodiments, wherein a default PUCCH group mayinclude at least one of a PUCCH group with a smallest PUCCH group ID ina current bandwidth part or a PUCCH group that includes services thatare the least delay tolerant.

In some embodiments, the UE may activate or deactivate at least oneantenna panel used for transmissions with the base station. In suchembodiments, the UE may report, to the base station, capabilitiesassociated with a quasi co-location (QCL) update. The capabilities mayinclude at least one of, one or more of, and/or both of a number (e.g.,a maximum number, in some embodiments) of supported transmissionconfiguration indicator (TCI) states across component careers (CCs)within a band or a number (e.g., a maximum number, in some embodiments)of PUCCH groups supported per BWP, within a cell, or across CCs within aband for a PUCCH. In some embodiments, active PUCCH resources fromdifferent component carriers overlapping in the time domain may beassociated with a PUCCH group for intra-band carrier aggregation orinter-band carrier aggregation.

In some embodiments, the UE may assign, during a measurement reportingprocedure, a logical antenna panel ID to a channel state informationreference signal (CSI-RS) resource indicator (CRI) or a synchronizationsignal/physical broadcast channel (SSB/PBCH) block resource indicator(SSBRI). In such embodiments, the UE may report, during the measurementreporting procedure, the logical antenna panel ID used for transmissionto and/or reception from the base station. In some embodiments, theCM/SSBRI may indicate a preferred beam. In some embodiments, theCRI/SSBRI may be a resource index for channel state informationreference signal (CSIRS) or synchronization signal block (SSB)). In someembodiments, the UE may report, during sounding reference signal (SRS)transmissions, a logical antenna panel ID used for SRS transmissions.

In some embodiments, the UE may provide, to the base station, anindication of an antenna panel switching time via one of a MAC-CE, radioresource control (RRC) signaling, or signaling via a PUCCH. In someembodiments, the indication may be on a per antenna panel basis. In someembodiments, antenna panels may be identified via logical antenna panelidentifiers (IDs). In some embodiments, the indication may be providedperiodically to the base station. In some embodiments, the indicationmay be provided a-periodically to the base station, e.g., when UEdecides to change a panel power management state. In some embodiments,the indication may be provided to the base station based on anoccurrence of an event. In such embodiments, the event may include atleast one of activation of an antenna panel, deactivation of an antennapanel, and/or switching to or from an antenna panel fortransmission/reception.

In some embodiments, the UE may report, to the base station, a minimumlatency requirement for switching antenna panels. In some embodiments,in response to the base station violating the minimum latencyrequirement, the UE may determine an antenna panel to use without inputfrom the base station. In some embodiments, in response to the basestation violating the minimum latency requirement, the UE may determinean antenna panel to use based on a pre-specified configuration. In suchembodiments, the pre-specified configuration may include one of the UEselecting a beam used for a control resource set (CORESET) with a lowestID in a current active antenna panel and/or the UE selecting a last beamused for reception and/or transmission in a current active antennapanel. In some embodiments, in response to the base station violatingthe minimum latency requirement, the UE may receive, from the basestation, an indication of a logical antenna panel ID to use formeasurements. In some embodiments, the report may be provided via one ofa MAC-CE, radio resource control (RRC) signaling, or signaling via aPUCCH.

In some embodiments, the UE may receive, from the base station, anupdate to a pathloss measurement reference signal (RS) via a MAC CE. Insome embodiments, when (if) the UE cannot (reliably) measure thepathloss measurement RS (e.g., at least once) prior to transmission of asubsequent sounding reference signal/physical uplink sharedchannel/PUCCH (SRS/PUSCH/PUCCH), the UE may continue to use pathlossestimate from a prior RS to determine the uplink open loop transmitpower until pathloss can be (reliably) measured from the new pathlossmeasurement RS.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users.

Embodiments of the present disclosure may be realized in any of variousforms. For example, some embodiments may be realized as acomputer-implemented method, a computer-readable memory medium, or acomputer system. Other embodiments may be realized using one or morecustom-designed hardware devices such as ASICs. Still other embodimentsmay be realized using one or more programmable hardware elements such asFPGAs.

In some embodiments, a non-transitory computer-readable memory mediummay be configured so that it stores program instructions and/or data,where the program instructions, if executed by a computer system, causethe computer system to perform a method, e.g., any of the methodembodiments described herein, or, any combination of the methodembodiments described herein, or, any subset of any of the methodembodiments described herein, or, any combination of such subsets.

In some embodiments, a device (e.g., a UE 106) may be configured toinclude a processor (or a set of processors) and a memory medium, wherethe memory medium stores program instructions, where the processor isconfigured to read and execute the program instructions from the memorymedium, where the program instructions are executable to implement anyof the various method embodiments described herein (or, any combinationof the method embodiments described herein, or, any subset of any of themethod embodiments described herein, or, any combination of suchsubsets). The device may be realized in any of various forms.

Although the embodiments above have been described in considerabledetail, numerous variations and modifications will become apparent tothose skilled in the art once the above disclosure is fully appreciated.It is intended that the following claims be interpreted to embrace allsuch variations and modifications.

What is claimed is:
 1. A base station, comprising: at least one antenna;at least one radio, wherein the at least one radio is configured toperform cellular communication using at least one radio accesstechnology (RAT); and one or more processors coupled to the at least oneradio, wherein the one or more processors and the at least one radio areconfigured to perform voice and/or data communications; and wherein theone or more processors are configured to cause the base station to:configure, via communications with a user equipment device (UE) servedby the base station, a group identifier (ID) for physical uplink controlchannel (PUCCH) resources within a group of PUCCHs; and transmit, to theUE, an update to one or more PUCCH resources within the group of PUCCHsvia a medium access control (MAC) control element (CE), wherein the MACCE includes one of a resource ID or the group ID.
 2. The base station ofclaim 1, wherein the one or more processors are further configured tocause the base station to: receive, from the UE, capabilities associatedwith a quasi co-location (QCL) update, wherein the QCL update is basedon activation or deactivation of at least one antenna panel used by theUE for transmissions with the base station.
 3. The base station of claim2, wherein the capabilities include at least one of: a number ofsupported transmission configuration indicator (TCI) states acrosscomponent careers (CCs) within a band; or a number of PUCCH groupssupported per BWP, within a cell, or across CCs within a band for aPUCCH.
 4. The base station of claim 1, wherein the one or moreprocessors are further configured to: receive, during a measurementreporting procedure, a logical antenna panel ID used by a UE fortransmission to and/or reception from the base station, wherein thelogical antenna panel ID was assigned during the measurement reportingprocedure to a channel state information reference signal (CSI-RS)resource indicator (CRI) or a synchronization signal/physical broadcastchannel (SSB/PBCH) block resource indicator (SSBRI), wherein the CRI orSSBRI indicates a preferred beam, and wherein the CRI or SSBRI is aresource index for channel state information reference signal (CSIRS) orsynchronization signal block (SSB).
 5. The base station of claim 1,wherein the one or more processors are further configured to: receive,during sounding reference signal (SRS) transmissions, a logical antennapanel ID used for SRS transmissions.
 6. An apparatus, comprising: amemory; and at least one processor in communication with the memory andconfigured to: configure, via communications with a user equipmentdevice (UE) served by a base station associated with the apparatus, agroup identifier (ID) for physical uplink control channel (PUCCH)resources within a group of PUCCHs; and generate instructions totransmit, to the UE, an update to one or more PUCCH resources within thegroup of PUCCHs via a medium access control (MAC) control element (CE),wherein the MAC CE includes one of a resource ID or the group ID.
 7. Theapparatus of claim 6, wherein the at least one processor is furtherconfigured to: receive, from the UE, an indication of an antenna panelswitching time via one of a MAC-CE, radio resource control (RRC)signaling, or signaling via a PUCCH.
 8. The apparatus of claim 7,wherein the indication is on a per antenna panel basis.
 9. The apparatusof claim 7, wherein the indication is received from the UE periodically,upon a change to a UE panel power management state, or based on anoccurrence of an event at the UE, and wherein the event at the UEincludes at least one of UE activation of an antenna panel, UEdeactivation of an antenna panel, or UE switching to or from an antennapanel for transmission/reception.
 10. A non-transitory computer readablememory medium storing program instructions executable by processingcircuitry to cause a base station to: configure, via communications witha user equipment device (UE) served by the base station, a groupidentifier (ID) for physical uplink control channel (PUCCH) resourceswithin a group of PUCCHs; and transmit, to the UE, an update to one ormore PUCCH resources within the group of PUCCHs via a medium accesscontrol (MAC) control element (CE), wherein the MAC CE includes one of aresource ID or the group ID.
 11. The non-transitory computer readablememory medium of claim 10, wherein the program instructions are furtherexecutable by processing circuitry to cause the base station to:receive, from the UE, an indication of a minimum latency requirement forthe UE to switch antenna panels wherein the indication of the minimumlatency requirement for the UE to switch antennal panels is provided viaone of a MAC-CE, radio resource control (RRC) signaling, or signalingvia a PUCCH s; and in response to violating the minimum latencyrequirement, transmit, to the UE, an indication of a logical antennapanel ID to use for measurements.
 12. The non-transitory computerreadable memory medium of claim 10, wherein the program instructions arefurther executable by processing circuitry to cause the base station to:receive, from the UE, capabilities associated with a quasi co-location(QCL) update, wherein the QCL update is based on activation ordeactivation of at least one antenna panel used by the UE fortransmissions with the base station.
 13. The non-transitory computerreadable memory medium of claim 12, wherein the capabilities include atleast one of: a number of supported transmission configuration indicator(TCI) states across component careers (CCs) within a band; or a numberof PUCCH groups supported per BWP, within a cell, or across CCs within aband for a PUCCH.
 14. The non-transitory computer readable memory mediumof claim 10, wherein the program instructions are further executable byprocessing circuitry to cause the base station to: receive, during ameasurement reporting procedure, a logical antenna panel ID used by a UEfor transmission to and/or reception from the base station.
 15. Thenon-transitory computer readable memory medium of claim 14, wherein thelogical antenna panel ID was assigned during the measurement reportingprocedure to a channel state information reference signal (CSI-RS)resource indicator (CRI) or a synchronization signal/physical broadcastchannel (SSB/PBCH) block resource indicator (SSBRI), wherein the CRI orSSBRI indicates a preferred beam, and wherein the CRI or SSBRI is aresource index for channel state information reference signal (CSIRS) orsynchronization signal block (SSB).
 16. A user equipment device (UE),comprising: at least one antenna; at least one radio, wherein the atleast one radio is configured to perform cellular communication using atleast one radio access technology (RAT); and one or more processorscoupled to the at least one radio, wherein the one or more processorsand the at least one radio are configured to perform voice and/or datacommunications; wherein the one or more processors are configured tocause the UE to: configure, via communications with a base stationserving the UE, a group identifier (ID) for physical uplink controlchannel (PUCCH) resources within a group of PUCCHs; receive, from thebase station serving the UE, an update to one or more PUCCH resourceswithin the group of PUCCHs via a medium access control (MAC) controlelement (CE), wherein the MAC CE includes one of a resource ID or thegroup ID; and update, based on the MAC CE, the one or more PUCCHresources within the group of PUCCHs.
 17. The UE of claim 16, whereinconfiguring the group ID comprises exchanging radio resource control(RRC) messages during a PUCCH configuration procedure.
 18. The UE ofclaim 16, wherein one of the resource ID, the group ID, a bandwidth partID, or a service cell ID indicates one of a reserved value or an invalidvalue, wherein, when the reserved value or the invalid value isreceived, the UE assumes that a single beam updates resources, bandwidthparts, component carriers, and/or groups associated with the UE.
 19. TheUE of claim 18, wherein the one or more processors are furtherconfigured to cause the UE to: interpret the MAC CE as at least one of:an update to PUCCH resources configured in a bandwidth part, wherein thebandwidth part is indicated via a bandwidth part identifier; an updateto PUCCH resources configured in cells serving the UE; or an update toPUCCH resources configured in a cell indicated by a service cellidentifier included in the MAC CE.
 20. The UE of claim 16, wherein adefault PUCCH group ID is defined or specified, wherein a default PUCCHgroup includes at least one of: a PUCCH group with a smallest PUCCHgroup ID in a current bandwidth part; or a PUCCH group that includesservices that are the least delay tolerant.